Ulrich Weigand writes:
>
> Eric Pouech wrote:
>
> > as posted by Uwe, exceptions were not properly handled when one
> > exception frame was located on the large stack.
> > this patch solves it (as tested by Uwe).
>
> Hmmm. This collides with a change I was working on :-/ Anyway, wouldn't
> it be simpler if CALL_LARGE_STACK would just adapt the TEB stack limits
> while executing on the large stack? This way, the NTDLL exception logic
> wouldn't need to know about all those special cases ...
>
> What do you think of the appended alternative patch?
I reversed Eric's patch and applied yours and now my crashing example
shows:
fixme:dc:GetDCEx new hrgnClip[0000] smashes the previous[43b2]
fixme:x11drv:error_handler BON:Xerror code 9
Xlib: unexpected async reply (sequence 0x6c64)!
fixme:seh:EXC_RtlRaiseException BON:res 1
fixme:seh:EXC_RtlRaiseException BON:Stack 0x40c56c44 invalid
fixme:seh:EXC_RtlRaiseException BON:signal_stack 0x40b41000 0x40b45000
err:seh:EXC_DefaultHandling Exception frame is not in stack limits => unable to
dispatch exception.
and wine keeps hanging there.
Those debugmsg with BON in it is added debug output.
Bye
Uwe Bonnes [EMAIL PROTECTED]
Free Software: If you contribute nothing, expect nothing
--
