Re: FW: Help debugging a problem!

2005-09-29 Thread Rein Klazes
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 >defined >- Stacks are identical as far as winedbg traces (0x60 bytes) Hi Jason, This winedbg stack trace (info stack) is equivalent to the exami

Re: FW: Help debugging a problem!

2005-09-29 Thread Marcus Meissner
On Wed, Sep 28, 2005 at 11:53:28PM +0100, Ann & Jason Edmeades wrote: > Ok, more information... > > The routine (slightly modified to allow code before the return) is > > ATOM WINAPI RegisterClass16( const WNDCLASS16 *wc ) > { > WNDCLASSEX16 wcex; > ATOM fred; >

Re: FW: Help debugging a problem!

2005-09-28 Thread James Hawkins
On 9/28/05, Ann & Jason Edmeades <[EMAIL PROTECTED]> wrote: > > Adding inchar temp[8]; before the WNDCLASSEX16 and it still fails > Adding inchar temp[9]; and the program starts working... > Adding inchar temp[9]; after the WNDCLASSEX16 and it still fails > (Yes, temp is unused...) > >

FW: Help debugging a problem!

2005-09-28 Thread Ann & Jason Edmeades
Ok, more information... The routine (slightly modified to allow code before the return) is ATOM WINAPI RegisterClass16( const WNDCLASS16 *wc ) { WNDCLASSEX16 wcex; ATOM fred; wcex.cbSize= sizeof(wcex); :