Re: Crash in MSG_PeekHardwareMsg

[gerard patel]

At 08:56 PM 12/05/2001 +0200, you wrote:
> 085a8b90:Ret  USER.114: DISPATCHMESSAGE() retval=0x00000000 ret=02ef:005c ds=033f
> 085a8b90:Call USER.108: GETMESSAGE(0x033fd1be,0x0000,0x0000,0x0000) ret=02ef:4055 ds=033f
> fixme:pthread_kill_other_threads_np
> ...
> Unhandled exception: page fault on read access to 0xffff0203
> in 32-bit code (0x40a1718f).
> In 32-bit mode.
> 0x40a1718f (MSG_PeekHardwareMsg+0x4f [message.c:595] in libkeyboard.so): repe movsl     (%esi),%
> es:(%edi)
> 597             nextqmsg = qmsg->nextMsg;

<snip>
> Any ideas?

There is not much to go on in this information. I can't see this problem with any
of my 16 bits apps, but maybe none of them use this kind of GetMessage without specifying
a window.

I'd suggest first that you compile message.c with optimization level O0 : it seems clear that the
displayed instruction is not the one responsible for the crash; the crash happens really in
*msg = qmsg->msg. Maybe having no optimization could give more accurate information.

When you have done that, rerun and enter info reg and info local when the crash 
occurs. Also a trace with +relay could be interesting but I think that you know that
since you post this tip on cemw often enough :-)

Gerard