FW: Help debugging a problem!
wijn at wanadoo.nl
Thu Sep 29 05:54:31 CDT 2005
On Wed, 28 Sep 2005 23:53:28 +0100, you wrote:
>I've tried the following
>1. Use DebugBreak before and after the RegisterClassEx16 call with no temp
>- Stacks are identical as far as winedbg traces (0x60 bytes)
This winedbg stack trace (info stack) is equivalent to the examine
x /24x $esp
(24 words == 0x60 bytes). Change the repeat count from 24 to what you
want. If there is a stack corruption, this way you can find out where
and then you can add a watch point on it.
More information about the wine-devel