Posts by Rom Walton (BOINC)

1) Message boards : RALPH@home bug list : Bug reports for Ralph 5.21 (Message 1788)
Posted 6 Jun 2006 by Rom Walton (BOINC)
Post:
Tony,

What kind of graphics adapter do you have on that machine?
2) Message boards : RALPH@home bug list : Debugger Stuff (Message 1176)
Posted 15 Apr 2006 by Rom Walton (BOINC)
Post:
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
3) Message boards : RALPH@home bug list : OLD- Bug reports for Windows Ver - 5.00 (and higher) (Message 1149)
Posted 14 Apr 2006 by Rom Walton (BOINC)
Post:
Son Goku,

If your willing, could you install:
http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.5.3.8.exe

If the symbol problem goes away, then that means the installation program is writing some registry value I need to find.

Thanks in advance.
4) Message boards : RALPH@home bug list : OLD- Bug reports for Windows Ver - 5.00 (and higher) (Message 1147)
Posted 14 Apr 2006 by Rom Walton (BOINC)
Post:
Son Goku,

Do you use a proxy server?

The reason I ask is, in the stacktraces your machine is generating, it keeps saying that it is using exported symbols. Exported symbols are only used when the debugger fails to actually connect up to MS to download the needed symbol files.

Right now the debugger isn't paying attention to the setting that are in BOINC, but I was hoping for better results for those with full time internet connections.

I would like to figure out the problem is to see if I can programatically fix it.
5) Message boards : RALPH@home bug list : Debugger Stuff (Message 1146)
Posted 14 Apr 2006 by Rom Walton (BOINC)
Post:
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...
6) Message boards : RALPH@home bug list : OLD- Bug reports for Windows Ver - 5.00 (and higher) (Message 1136)
Posted 13 Apr 2006 by Rom Walton (BOINC)
Post:
Son Goku,

Is your computer offline, when these errors occur on 5.4.1?

----- Rom
7) Message boards : RALPH@home bug list : OLD- Bug reports for Windows Ver - 5.00 (and higher) (Message 1103)
Posted 12 Apr 2006 by Rom Walton (BOINC)
Post:
Most of the useful diagnostic information we can only get from the new 5.4.x clients.

Since this is an alpha test project and all, it would help a great deal to upgrade to 5.4.x.

----- Rom
8) Message boards : RALPH@home bug list : Win98 error starting program [closed] (Message 995)
Posted 26 Mar 2006 by Rom Walton (BOINC)
Post:
Do'h...

Okay, I'll get them to rebuild against the latest BOINC API.

I didn't realize that OpenThread wasn't added until WinME.

Sorry about that.

----- Rom
9) Message boards : RALPH@home bug list : Report \"stuck at 1%\" bugs here (Message 958)
Posted 23 Mar 2006 by Rom Walton (BOINC)
Post:
For those who are searching for this bug could you upgrade your BOINC client to 5.3.28 or better?

Apparently the 5.2.x clients don't send the right instruction to the application when it is time to abort to cause it to dump the backtraces for the various threads.

Sorry about that. 5.3.x has been in the oven for quite awhile and I forgot what I was hooking into wasn't supported by the older client.

----- Rom
10) Message boards : RALPH@home bug list : RALPH Version News! - Version 4.94 released! (Message 939)
Posted 22 Mar 2006 by Rom Walton (BOINC)
Post:
For those who are running any of the older releases, please reset the RALPH project to pick up the new bits.

This release contains all the fixes from the previous release plus some additional enhancements to track down the '1% bug.'

When a workunit is aborted additional information is going to be logged with the result when it is reported back to the server.

Here is what some of that additional information looks like. This additional information shows where the program was at and what it was doing at the time that you aborted it. With enough of these we should get a pretty good idea where the '1% bugs' are comming from.

The previous method for dealing with this bug involved using a debugger on a remote machine and creating a usermode dump file. For those who don't know what that is, it is a 350MB file that contains all the data the program was managing at the time the dump was taken. It proved to be to labor intensive to walk many people through the process and get the dump files over email. So with a little bit of tweaking last night I adjusted things so that I could get the information when you all abort the workunits.

So if you abort a workunit because of the '1% bug' on Ralf please log the result id here

Thanks in advance.

----- Rom
11) Message boards : RALPH@home bug list : Report \"stuck at 1%\" bugs here (Message 936)
Posted 20 Mar 2006 by Rom Walton (BOINC)
Post:
Could you send it to this address:

romw at romwnet.org

It is currently setup with unrestricted sizes for sending and receiving email.

----- Rom

I sent you an email with the following content... did you get it?

"Looks like I’m having trouble getting the 12 meg out of the gate here. My main email ISP has a 5 meg limit, another has a 10 meg limit (both I have direct access to).. yet another ISP I have an account with is unlimited, but I have no direct connection with them and they don’t allow relaying… So It looks like I am going to have to carve the files up. Do you have a preferred method? I can create segmented Zips, or there is a shareware program I have used in the past called EZSplit. Or I could just write a short program to cut it up."

Mike



I didn't get it. Go ahead and create mini rars then, winrar can break up the dump file and reassemble it without to much grief.

----- Rom
12) Message boards : RALPH@home bug list : Report \"stuck at 1%\" bugs here (Message 934)
Posted 20 Mar 2006 by Rom Walton (BOINC)
Post:
Could you send it to this address:

romw at romwnet.org

It is currently setup with unrestricted sizes for sending and receiving email.

----- Rom
13) Message boards : RALPH@home bug list : Report \"stuck at 1%\" bugs here (Message 932)
Posted 20 Mar 2006 by Rom Walton (BOINC)
Post:
well go ahead and get a dump of it. I'm glad it at least repro'ed for you.

----- Rom
14) Message boards : RALPH@home bug list : Report \"stuck at 1%\" bugs here (Message 929)
Posted 19 Mar 2006 by Rom Walton (BOINC)
Post:
Ah, okay...

Well hopefully it'll do it again...

Let me know how it goes...
15) Message boards : RALPH@home bug list : Report \"stuck at 1%\" bugs here (Message 926)
Posted 19 Mar 2006 by Rom Walton (BOINC)
Post:
Mike,

Are you familiar with the Windows debugging tools?

The reason I ask, is if I could get a dump of the process this might go quite a bit quicker.

Would you be game for trying to get me a dump?

This is why I was suggesting direct contact. I am familiar with VS tools for remote debugging, but I always have the source where I can attach to a remote process and set breakpoints and such. How to debug without source is something I'm not sure about. (Never had to, so never I figured it out).


Sweet.

Attach to the process with Visual Studio.
Break on all threads
From the debug menu select Save Dump As.
Be sure to change the dump type to dump with heap.
And give it some sort of name.

With winzip compression the fire should shrink to 20MB or so.

Do you have a web server I would be able to dl it from? Or should we try email?

----- Rom
16) Message boards : RALPH@home bug list : Report \"stuck at 1%\" bugs here (Message 915)
Posted 19 Mar 2006 by Rom Walton (BOINC)
Post:
Mike,

Are you familiar with the Windows debugging tools?

The reason I ask, is if I could get a dump of the process this might go quite a bit quicker.

Would you be game for trying to get me a dump?
17) Message boards : RALPH@home bug list : Report \"stuck at 1%\" bugs here (Message 908)
Posted 19 Mar 2006 by Rom Walton (BOINC)
Post:
Mike,

Using Process Explorer again, can you look at the thread state for each thread?

What is the base priority and dynamic priority for each thread in your list?

It should be visible on the Threads tab on the process properties dialog box.

TIA.

----- Rom
18) Message boards : RALPH@home bug list : Report \"stuck at 1%\" bugs here (Message 905)
Posted 18 Mar 2006 by Rom Walton (BOINC)
Post:
Oppps, forgot to ask you to do one additional thing....

In Process Explorer there is an Options menu... Configure Symbols...

Can you set the Dbghelp.dll path to:

C:Program FilesBOINCDbgHelp.dll

After that could you rerun the tests again?

When things are working right you'll get something that looks like this:
rosetta_beta_4.93_windows_intelx86.exe!pairenergy+0x126
rosetta_beta_4.93_windows_intelx86.exe!fullatom_energy+0x1979
rosetta_beta_4.93_windows_intelx86.exe!scorefxn+0xb4e

TIA.

----- Rom
19) Message boards : RALPH@home bug list : Report \"stuck at 1%\" bugs here (Message 901)
Posted 18 Mar 2006 by Rom Walton (BOINC)
Post:
Probably the best thing to do is get this tool:
http://www.sysinternals.com/Utilities/ProcessExplorer.html

Open up process explorer.
Right-Click on the Rosetta process and bring up the properties.
Switch to the threads tab.
For each thread that is eating CPU time click on the stack button.
Click on the copy button.

Do that a few times and post the results here.

----- Rom






©2020 University of Washington
http://www.bakerlab.org