Re: automated stack dumps broken, just output winedbg usage message now?

2010-06-25 Thread Eric Pouech

Le 26/06/2010 01:58, Dan Kegel a écrit :

Is anybody else seeing winedbg fail to generate stack dumps?
I'm seeing

wine: Unhandled page fault on read access to 0x at address
0xb736bd68 (thread 0009), starting debugger...
Usage:
 winedbg [ [ --gdb ] [ prog-name [ prog-args ] |  |
file.mdmp | --help ]

on a lot of apps when they crash.   Could be me, but I figured I'd ask.

This is with wine-1.2-rc3.




   

maybe your AeDebug registry entry is broken (in system.reg)
it should read (for a standard install):

[Software\\Microsoft\\Windows NT\\CurrentVersion\\AeDebug] 1274602108
"Auto"="1"
"Debugger"="winedbg --auto %ld %ld"

or (if you want to still use the debugger when a crash happens)

[Software\\Microsoft\\Windows NT\\CurrentVersion\\AeDebug] 1274602108
"Auto"="1"
"Debugger"="winedbg %ld %ld"

A+
--

Eric Pouech
"The problem with designing something completely foolproof is to underestimate the 
ingenuity of a complete idiot." (Douglas Adams)







automated stack dumps broken, just output winedbg usage message now?

2010-06-25 Thread Dan Kegel
Is anybody else seeing winedbg fail to generate stack dumps?
I'm seeing

wine: Unhandled page fault on read access to 0x at address
0xb736bd68 (thread 0009), starting debugger...
Usage:
winedbg [ [ --gdb ] [ prog-name [ prog-args ] |  |
file.mdmp | --help ]

on a lot of apps when they crash.   Could be me, but I figured I'd ask.

This is with wine-1.2-rc3.