Re: FW: Help debugging a problem!

[Rein Klazes]

On Wed, 28 Sep 2005 23:53:28 +0100, you wrote:
> I've tried the following
> - Use DebugBreak before and after the RegisterClassEx16 call with no temp
>
> defined
> - Stacks are identical as far as winedbg traces (0x60 bytes)

Hi Jason,

This winedbg stack trace (info stack) is equivalent to the examine
command:

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.

Rein.