wine at mkarcher.dialup.fu-berlin.de
Sun Jul 13 04:26:30 CDT 2008
Am Samstag, den 12.07.2008, 20:52 -0400 schrieb Seth Shelnutt:
> zerix01 at DeepThought:~/.wine/drive_c/Program Files/Folding at home/Folding at home-gpu$ winedbg Folding at home.exe
> WineDbg starting on pid 0024
> start_process () at /media/md0/wine/wine/dlls/kernel32/process.c:904
> 0x7b877d02 start_process+0xc2 [/media/md0/wine/wine/dlls/kernel32/process.c:904] in kernel32: movl %esi,0x0(%esp)
> 904 ExitThread( entry( peb ) );
> fixme:d3d:IWineD3DImpl_FillGLCaps OpenGL implementation supports 32 vertex samplers and 32 total samplers
> fixme:d3d:IWineD3DImpl_FillGLCaps Expected vertex samplers + MAX_TEXTURES(=8) > combined_samplers
> fixme:win:EnumDisplayDevicesW ((null),0,0x33f40c,0x00000000), stub!
> err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0xf7facaaf
> Invalid address (0x7b877d07 start_process+0xc7) for breakpoint 0, disabling it
> Process of pid=0024 has terminated
> I believe the key line is Invalid address (0x7b877d07 start_process
> +0xc7) for breakpoint 0, disabling it.
No, thats boring. Your program crahsed at address 0xf7fcaaf. IIRC code
0xc0000005 is a general protection fault. After your program has
crashed, the breakpoint wine automatically sets to catch program startup
is not valid anymore (there is no program to break anymore), that causes
the message you quoted.
Whats strange is that the debugger does not catch the exception. While
the first-chance event can be disabled, you should get a last-chance
exception catch right before the program dies. See
http://www.winehq.org/site/docs/winedev-guide/dbg-config for more info
about configuring the debugger.
Have you tried a relay trace yet?
More information about the wine-devel