Uwe Bonnes wrote:
> My other wish is that __TRY __EXCEPT was handled on the big stack too.
> In my source tree the failing function (XCopyArea) is surrounded
> by a __TRY clause and the corresponding __EXCEPT is not yet
> entered. The debugger in entered via XSetErrorHandler -> error_handler
> -> DebugBreak.
> Is this possible to dispatch the exception? I tried to find
> documentation on the error-code that xlib delivers, but didn't find
> anything yet.
Well, if X decides to call the error handler, that's beyond our control.
The only thing we can to is to decide what the error handler does. At
the moment it calls DebugBreak, which in effect raises an exception
with code EXCEPTION_BREAKPOINT. Does your __EXCEPT filter check for
this code? If so, the __EXCEPT block should be called ... Alternatively,
you might decide to raise another exception in the X error handler,
maybe depending on the particular error.
This should work on the large stack as well as otherwise.
Bye,
Ulrich
--
Dr. Ulrich Weigand
[EMAIL PROTECTED]
