Re: kernel32: Intialise 16-bit stack to zero.

[Alexandre Julliard]

Robert Shearman  writes:
> dlls/kernel32/kernel_main.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>
> Otherwise dbghelp could sometimes get confused and think it should
> switch to 16-bit mode.
> This results in messages such as the following when warn or tracing
> for the heap channel is turned on:
> fixme:dbghelp:Failed to linearize address ????:55555555 ...

Initializing the first frame should be enough.

kernel32: Intialise 16-bit stack to zero.

[Robert Shearman]

Alexandre Julliard wrote:
> Robert Shearman  writes:
> > Otherwise dbghelp could sometimes get confused and think it should
> > switch to 16-bit mode.
> > This results in messages such as the following when warn or tracing
> > for the heap channel is turned on:
> > fixme:dbghelp:Failed to linearize address ????:55555555 ...
>
> Initializing the first frame should be enough.

I can't work out what the size of the first frame is though. Is it 
sizeof(STACK16FRAME)?

kernel32: Intialise 16-bit stack to zero.

[Alexandre Julliard]

Robert Shearman  writes:
> Alexandre Julliard wrote:
> > Initializing the first frame should be enough.
>
> I can't work out what the size of the first frame is though. Is it
> sizeof(STACK16FRAME)?

Yes; NtCurrentTeb()->WOW32Reserved is set to point to the initial stack
frame at the top of the stack, that's what you have to initialize.