http://bugs.winehq.org/show_bug.cgi?id=21389
Summary: Debugger does not start when application crashes Product: Wine Version: 1.1.36 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P4 Component: winedbg AssignedTo: wine-bugs@winehq.org ReportedBy: ayers@fsfe.org
I'm trying to capture trace for bug in a game, yet it seems I'm having issues creating a useful log. I have followed the instructions:
http://wiki.winehq.org/FAQ#head-a37de3282d447376d2220d20a278ae52258551a4
and obtained a log which ends with:
fixme:cursor:SetSystemCursor (0x1226,00007f02),stub! fixme:win:EnumDisplayDevicesW ((null),0,0x3d0eb54,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x3d0ed3c,0x00000000), stub! fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x1644a0,0x1672a0): stub fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x1644a0,0x1672a0): stub fixme:d3d:WineD3D_ChoosePixelFormat Add OpenGL context recreation support to SetDepthStencilSurface fixme:d3d9:Direct3DShaderValidatorCreate9 stub wine: Unhandled page fault on read access to 0x00000000 at address 0x3f12bd (thread 0009), starting debugger... err:seh:start_debugger Couldn't start debugger ("winedbg --auto 8 5752") (2) Read the Wine Developers Guide on how to set up winedbg or another debugger
So I've read through: http://www.winehq.org/docs/winedev-guide/dbg-config
and found that my registry entry for [MACHINE\Software\Microsoft\Windows NT\CurrentVersion\AeDebug] contains:
Debugger REG_SZ winedbg --auto %ld %ld
I assume the --auto is expected even though it is not mentioned in the FAQ.
Please advise on how I can get the wine debugger configured correctly.