Over the last couple of weeks I've been adding features to the BOINC Windows Debugger, which is based on Microsoft's DBGHELP.DLL and Stackwalker.

Many of these changes required a newer version of DBGHELP.DLL than what came with BOINC 5.2.x. which is why I have been suggesting to people to upgrade to 5.4.x.

Here is an example of the output that the new software produces when a crash happens.

BOINC Windows Debugger  Version 5.5.0

Dump Timestamp    : 04/13/06 23:09:47
Debugger Engine   : 4.0.5.0
Symbol Search Path: C:Program FilesBOINCslots5;C:Program FilesBOINCprojectsralph.bakerlab.org;srv*c:windowssymbols*http://msdl.microsoft.com/download/symbols;srv*C:DOCUME~1romwLOCALS~1Tempsymbols*http://boinc.berkeley.edu/symstore


ModLoad: 00400000 00712000 C:Program FilesBOINCprojectsralph.bakerlab.orgrosetta_beta_5.00_windows_intelx86.exe (PDB Symbols Loaded)
ModLoad: 7c800000 000c0000 C:WINDOWSsystem32ntdll.dll (PDB Symbols Loaded)
ModLoad: 77e40000 00102000 C:WINDOWSsystem32kernel32.dll (PDB Symbols Loaded)
ModLoad: 76aa0000 0002d000 C:WINDOWSsystem32WINMM.dll (PDB Symbols Loaded)
ModLoad: 77f50000 0009c000 C:WINDOWSsystem32ADVAPI32.dll (PDB Symbols Loaded)
ModLoad: 77c50000 0009f000 C:WINDOWSsystem32RPCRT4.dll (PDB Symbols Loaded)
ModLoad: 77c00000 00048000 C:WINDOWSsystem32GDI32.dll (PDB Symbols Loaded)
ModLoad: 77380000 00092000 C:WINDOWSsystem32USER32.dll (PDB Symbols Loaded)
ModLoad: 5e8d0000 000ce000 C:WINDOWSsystem32OPENGL32.dll (PDB Symbols Loaded)
ModLoad: 77ba0000 0005a000 C:WINDOWSsystem32msvcrt.dll (PDB Symbols Loaded)
ModLoad: 68720000 00020000 C:WINDOWSsystem32GLU32.dll (PDB Symbols Loaded)
ModLoad: 73860000 0004c000 C:WINDOWSsystem32DDRAW.dll (PDB Symbols Loaded)
ModLoad: 73b30000 00006000 C:WINDOWSsystem32DCIMAN32.dll (PDB Symbols Loaded)
ModLoad: 4b8d0000 00051000 C:WINDOWSsystem32MSCTF.dll (PDB Symbols Loaded)
ModLoad: 0c430000 00118000 C:Program FilesBOINCdbghelp.dll (PDB Symbols Loaded)
ModLoad: 0c650000 00046000 C:Program FilesBOINCsymsrv.dll (PDB Symbols Loaded)
ModLoad: 0c6a0000 00031000 C:Program FilesBOINCsrcsrv.dll (PDB Symbols Loaded)


*** UNHANDLED EXCEPTION ****
Reason: Access Violation (0xc0000005) at address 0x00736DDA read attempt to address 0x06BAFC10

*** Dump of the Worker(offending) thread: ***
eax=0000015a ebx=05dbe624 ecx=fffffefc edx=06bb0020 esi=0b0476d8 edi=0b08eb74
eip=00736dda esp=05dbe4e8 ebp=05dbe63c
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00010217

ChildEBP RetAddr  Args to Child
05dbe4f8 0085e191 00a26fd4 ffffffff 0b0476d8 rosetta_beta_5.00_windows_intel!fast_pairenergy_hydrogens+0x4 (c:rosettasrctrunkrosetta++pack.cc:6165) FPO: [non-Fpo] 
05dbe588 0086596a 0b0476d8 0b08eb74 0000000a rosetta_beta_5.00_windows_intel!rotamer_trie::atom_atom_energy+0x0 (c:rosettasrctrunkrosetta++rotamer_descriptor.cc:3873) FPO: [non-Fpo] 
05dbea1c 00866e63 0b41ede8 05dbeab8 05dbeb24 rosetta_beta_5.00_windows_intel!rotamer_trie::trie_vs_background_i_ip3orMore+0x0 (c:rosettasrctrunkrosetta++rotamer_descriptor.cc:3492) FPO: [non-Fpo] 
05dbea6c 0086cc79 0b41ede8 00a26e4c ffffffff rosetta_beta_5.00_windows_intel!rotamer_trie::trie_vs_background+0x0 (c:rosettasrctrunkrosetta++rotamer_descriptor.cc:1048) FPO: [non-Fpo] 
05dbed88 0087eee6 0b0a5150 0000003e 0000000c rosetta_beta_5.00_windows_intel!trie_trials_energies+0x1bb (c:rosettasrctrunkrosetta++rotamer_trials.cc:1273) FPO: [non-Fpo] 
05dbf640 0087f37d 00a27084 0000141c 06fb8af8 rosetta_beta_5.00_windows_intel!fullatom_rotamer_trials_trie+0x0 (c:rosettasrctrunkrosetta++rotamer_trials.cc:1110) FPO: [non-Fpo] 
05dbf710 00899bbd 00000026 646409ba 05dbfa3b rosetta_beta_5.00_windows_intel!rotamer_trials+0x4b (c:rosettasrctrunkrosetta++rotamer_trials.cc:132) FPO: [non-Fpo] 
05dbf818 0089a8ea 646406be 05dbf848 009844f8 rosetta_beta_5.00_windows_intel!scorefxn+0x0 (c:rosettasrctrunkrosetta++score.cc:320) FPO: [non-Fpo] 
05dbf850 0070af4e 646406c6 0089a760 00000005 rosetta_beta_5.00_windows_intel!score12+0x5 (c:rosettasrctrunkrosetta++score.cc:1161) FPO: [non-Fpo] 
05dbf9fc 00913e08 05dbfb2c 05dbfabc 0089a760 rosetta_beta_5.00_windows_intel!minimize+0x7 (c:rosettasrctrunkrosetta++minimize.cc:512) FPO: [non-Fpo] 
05dbfae4 00852509 00000005 0089a760 00000009 rosetta_beta_5.00_windows_intel!main_small_min_trial+0x1e (c:rosettasrctrunkrosetta++torsion_bbmove_trials.cc:883) FPO: [non-Fpo] 
05dbfbdc 00409c42 00a43b94 0000000f 0000000f rosetta_beta_5.00_windows_intel!fullatom_relax+0x39 (c:rosettasrctrunkrosetta++relax_structure.cc:459) FPO: [non-Fpo] 
05dbfbf4 006e1100 6464029a 00000000 00000000 rosetta_beta_5.00_windows_intel!std::basic_string<char,std::char_traits<char>,std::allocator<char> >::operator=+0x21 (c:program filesmicrosoft visual studio 8vcincludexstring:882) FPO: [non-Fpo] 
05dbffb4 00629ee0 77e66063 00000000 00000000 rosetta_beta_5.00_windows_intel!main_rosetta+0x0 (c:rosettasrctrunkrosetta++main.cc:282) FPO: [non-Fpo] 
05dbffb8 77e66063 00000000 00000000 00000000 rosetta_beta_5.00_windows_intel!foobar+0x0 (c:rosettasrctrunkboincapigraphics_impl.c:75) FPO: [non-Fpo] 
05dbffec 00000000 00629ed0 00000000 00000000 kernel32!_BaseThreadStart@8+0x0 (c:rosettasrctrunkboincapigraphics_impl.c:75) FPO: [non-Fpo] 

*** Dump of the Timer thread: ***
eax=8347fb60 ebx=00000000 ecx=00000001 edx=079257d2 esi=00000001 edi=00000000
eip=7c82ed54 esp=05ebff0c ebp=05ebffb8
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246

ChildEBP RetAddr  Args to Child
05ebff08 7c822114 76aba0d3 00000002 05ebff70 ntdll!_KiFastSystemCallRet@0+0x0 FPO: [0,0,0] 
05ebff0c 76aba0d3 00000002 05ebff70 00000001 ntdll!_NtWaitForMultipleObjects@20+0x0 FPO: [5,0,0] 
05ebffb8 77e66063 00000000 00000000 00000000 WINMM!_timeThread@4+0x0 FPO: [non-Fpo] 
05ebffec 00000000 76aba099 00000000 00000000 kernel32!_BaseThreadStart@8+0x0 FPO: [non-Fpo] 

*** Dump of the Graphics thread: ***
eax=00000000 ebx=7738e3f7 ecx=0012ed50 edx=00000000 esi=0012ee2c edi=7739ca9d
eip=7c82ed54 esp=0012ede0 ebp=0012ee04
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000246

ChildEBP RetAddr  Args to Child
0012eddc 7739c78d 77392f3a 0012ee2c 00000000 ntdll!_KiFastSystemCallRet@0+0x0 FPO: [0,0,0] 
0012ee04 0093d8bf 0012ee2c 00000000 00000000 USER32!_NtUserGetMessage@16+0x0 
0012eedc 0062a185 00000001 00000001 00000001 rosetta_beta_5.00_windows_intel!win_graphics_event_loop+0x14 (c:rosettasrctrunkboincapiwindows_opengl.c:571) FPO: [non-Fpo] 
0012eefc 00629d2b 006e05f0 00af9294 006e1dff rosetta_beta_5.00_windows_intel!boinc_init_graphics_impl+0x32 (c:rosettasrctrunkboincapigraphics_impl.c:84) FPO: [non-Fpo] 
0012ef08 006e1dff 006e05f0 00000002 006e1e45 rosetta_beta_5.00_windows_intel!boinc_init_graphics+0x4b (c:rosettasrctrunkboincapigraphics_api.c:45) FPO: [non-Fpo] 
0012ef14 006e1e45 0000002c 0012ef2c 00152490 rosetta_beta_5.00_windows_intel!main+0x0 (c:rosettasrctrunkrosetta++main.cc:111) FPO: [non-Fpo] 
0012ff28 0095cba4 00400000 00000000 001524d3 rosetta_beta_5.00_windows_intel!WinMain+0x0 (c:rosettasrctrunkrosetta++main.cc:404) FPO: [non-Fpo] 
0012ffc0 77e523cd 00000000 00000000 7ffd9000 rosetta_beta_5.00_windows_intel!__tmainCRTStartup+0x1c (f:rtmvctoolscrt_bldself_x86crtsrccrt0.c:315) FPO: [non-Fpo] 
0012fff0 00000000 0095cc0d 00000000 78746341 kernel32!_BaseProcessStart@4+0x0 (f:rtmvctoolscrt_bldself_x86crtsrccrt0.c:315) FPO: [non-Fpo] 

Exiting...

---

for the peopl that do not know, 5.4.x is not in official/recommended release so you'll need to look on the development page as well.

i.e.

http://boinc.berkeley.edu/download.php?min_version=5.0&dev=1

---

Over the last couple of weeks I've been adding features to the BOINC Windows Debugger, which is based on Microsoft's DBGHELP.DLL and Stackwalker.

Many of these changes required a newer version of DBGHELP.DLL than what came with BOINC 5.2.x. which is why I have been suggesting to people to upgrade to 5.4.x.

OK, then I will grab the new DBGHELP.DLL that comes with 5.4.x,
and replace it on my boinc 5.2.13 folder.

Unless this does not work at all after I reboot,
there will the new debugger available.

BTW: Why Microsoft does not update DBGHELP.DLL via Windows/Microsoft Update ?
I have service pack 4 installed , and are up-to-date with every update !

---

Click signature for global team stats

Hi! I realized that DBGHELP.DLL may not suffice to do a good degug

Then, I downloaded this
http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.5.3.8.exe

Installed, and then copied these dlls to my BOINC directory , ops Folder

Volume in drive C is WIN2KAS
Volume Serial Number is 83F8-DF22

Directory of C:Program FilesDebugging Tools for Windows

05/24/2005 08:38a 2,608,128 dbgeng.dll
05/24/2005 08:37a 1,038,848 dbghelp.dll
05/24/2005 08:36a 406,016 decem.dll
05/24/2005 08:38a 78,848 srcsrv.dll
05/24/2005 08:38a 20,992 symbolcheck.dll
05/24/2005 08:38a 115,200 symsrv.dll
6 File(s) 4,268,032 bytes
0 Dir(s) 1,242,589,184 bytes free

C:Program FilesDebugging Tools for Windows>psftp boinc@roberto.dnsalias.com
Using username "boinc".
boinc@roberto.dnsalias.com's password:
Remote working directory is /home/boinc
psftp> cd MERFBO
Remote directory is now /home/boinc/MERFBO
psftp> put dbgeng.dll
local:dbgeng.dll => remote:/home/boinc/MERFBO/dbgeng.dll
psftp> put dbghelp.dll
local:dbghelp.dll => remote:/home/boinc/MERFBO/dbghelp.dll
psftp> put decem.dll

Let me know if the debugger works how u want on all my windows pcs,
disregard what boinc version I use -:

Thanks

---

Click signature for global team stats

You'll need to copy over symsrv.yes as well, otherwise it'll lock up at a EULA dialog MS wants you to agree too before using the symbol server.

:)

----- Rom

---

Hi! I realized that DBGHELP.DLL may not suffice to do a good degug

Yeah, this is what I ran into after updating to 5.4.1... It still didn't do it, so grabbed that. However 5.0 seems to be working (just got a WU in with a 4 hour time setting, so trying 8 hours now). From there, can't say more from a testing standpoint...

BTW, though it is in beta (the CC), and yes this project is an alpha/beta project itself; I can say that LHC was returning results OK, and CPDN seems to be running fine. I also asked on their boards, also explaining the situation over here and reason for grabbing this, and one of the mods on the CPDN project indicated that he tried 5.4.0 and it was working OK on CPDN for him.

Just running seasonal attribution now (to let it catch up), and will see after further testing, but all seems fine, as did when I allowed predictor to grab a few WUs. Others might have issues on some projects, and I haven't tested all I'm connected to. Note also, a few like malaria control I can't get to anyhow, so can't speak for...

---

<offtopic> I can't see why it wouldn't work with other porjects. Since all 5.4.x really is, is a bug fixes and some added features to 5.2.13
If you want to see the 'change log' look at the Mac's changlog it shows the alterations (that are probably relevant) throughout the development (5.3.x series). Don't know why the Mac log has them and the windows only starts from 5.4.0

Mind I have 5.3.31 running and it's fine on all the projects I run so far. Actually a lot better than 5.2.13, so thank's to Rom and the rest of the boinc dev team.

---

You'll need to copy over symsrv.yes as well, otherwise it'll lock up at a EULA dialog MS wants you to agree too before using the symbol server.

:)

----- Rom

In addition Copied more these 3
symsrv.yes
tlist.exe
kill.exe

The last two seems to be working -:)
H:boincBOINC>tlist | grep MB
2660 CMD.EXE Command Prompt - grep MB
2712 MBM5.EXE

H:boincBOINC>kill -f 2712
process MBM5.EXE (2712) - '' killed

H:boincBOINC>tlist | grep MB

H:boincBOINC>
ps: Who will agree to the EULA when I am asleeping -or away ?
How do I use the symbol server ?

---

Click signature for global team stats

<offtopic> I can't see why it wouldn't work with other porjects. Since all 5.4.x really is, is a bug fixes and some added features to 5.2.13
If you want to see the 'change log' look at the Mac's changlog it shows the alterations (that are probably relevant) throughout the development (5.3.x series). Don't know why the Mac log has them and the windows only starts from 5.4.0

Mind I have 5.3.31 running and it's fine on all the projects I run so far. Actually a lot better than 5.2.13, so thank's to Rom and the rest of the boinc dev team.

Typically, one would expect that it would. But sometimes, some project servers get picky about CC versions... If you've crunched a CPDN result before, you'll know wny some give it some thought. This coupled ocean model will likely take > 1,800 hours crunch time on my Athlon 64, which mind you, an Athlon 64 isn't exactly an average computer, performance wise. The deadline on these is greater then 1 year, if that also gives some idea... Yeah, people who crunch CPDN end up learning they need to be careful with it. Too many sulpher units for instance have gone south on people, and for smaller things then an upgrade. For instance, it doesn't well handle another process using 100% CPU time if it's running, and could easily get "out of sync"...

BTW, some servers were being taken offline for additional support (aka server version 5.5.0), with notes that it was in anticipation of the next CC. Probably support for the extra debugging and what not...

---

I re-read this thread and find it very confusing -:(

Thus I resume / simplify here what everyone that runs ralph@home needs to do

in order to allow developers find the bugs of Rosetta more efficiently -:)

Upgrade to latest boinc 5.4.x
http://boinc.berkeley.edu/download.php?min_version=5.0&dev=1
-or-
keep u current version of boinc and download this debugger - about 13 MB
http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.5.3.8.exe
Install it
*after installation,
copy from installation Folder all dll and all yes to u boinc folder
copy *.dll x:boinc_folder
copy *.yes x:boinc_folder
*u are done

PS: together with the debugger
comes
tlist.exe
kill.exe
that can be used on cmd prompt to list all running process
and if u want to kill some u may enter kill nnnn where nnnn is the process number

---

Click signature for global team stats

Carlos,

Yes, I agree it was confusing. But what I think I understand is that all I have to do to have the new debugger installed is to use the newer 5.4.x versions of the BOINC CC.
I usually try to run with the latest, so no problems there. Running with 5.4.4 everywhere now. I saw the new files in the Boinc folder, so hopefully everything's OK.

---

...
*after installation,
copy from installation Folder all dll and all yes to u boinc folder
copy *.dll x:boinc_folder
copy *.yes x:boinc_folder
*u are done

HM, thats really all ?

I just installed the debugger on my first machine, and now, I see a lot of sub-directories.

So, first question: Copy only files from "installation folder" or also from sub-folder, e.g. winxp ?

Second question: If I want to bring it up on next machine, could it be copied from the first or should it be installed first and then copied ?

Third question: Will it be okay for use on WIN2K-Server, WIN XP and WIN2K3-Server ?

fourth question: Should I download additional pdb-files from BOINC additional ?


A lot of questions :-)

---

Supporting BOINC, a great concept !

I just installed the debugger on my first machine, and now, I see a lot of sub-directories.

So, first question: Copy only files from "installation folder" or also from sub-folder, e.g. winxp ?

a. The "installation folder" suffice -> tlist.exe and kill.exe are there too

my installation folder is C:Program FilesDebugging Tools for Windows>
*this may be different on other PCs

Second question: If I want to bring it up on next machine, could it be copied from the first or should it be installed first and then copied ?

a. can copy from 1ST PC "installation folder" to the next PC boinc folder
*no need to install the debugger again on next PC

Third question: Will it be okay for use on WIN2K-Server, WIN XP and WIN2K3-Server ?

a. *I think yes, I installed on win2k-adv-server and copied to winxp-professional
boinc_folder w/o installing again there

fourth question: Should I download additional pdb-files from BOINC additional ?

a. I did not understand ... Ralph auto download the .pdb Rosetta do not

so, If u are plenty of disk-space, u can download the .pdb to Rosetta too

Thus,
If a error happens on Rosetta, the developers will have better debugging
on Rosetta app too.

or is any other .pdb u are referring to ? If so post the link to there.

---

Click signature for global team stats

Carlos,

I'm working with RW on the theme of "Chrashes while up-/downloading". I'm shure, you have seen my messages in BOINC_ALPHA_mailing_list. There, I only use my real-name, no nick ;-)

Shure there are more pdb_files, for BOINC_MGR, BOINC_EXE and so on. I have to search for the link in the deepness of my mail-programm.

But this is not a theme for debugging rosetta ...

Greetings and thanks for your help

---

Supporting BOINC, a great concept !

There is a new BOINC 5.4.5

http://boinc.berkeley.edu/download.php?dev=1

Anders n

---

and 5.4.6 isn't far off either.

and 5.4.6 isn't far off either.

I think I'll wait for that. Have 5.4.4 at the moment.

---

[color=navy][b]"I'm trying to maintain a shred of dignity in this world." - Me[/b][/color]