Eric Pouech wrote:
> well, for some winelib applications I don't think so.
Why should this be different for WineLib apps? IMO the large stack
is something completely internal to Wine, and should not interact
in any way with the application's (whether Win32 or WineLib) exception
handling. Everything executed on the large stack is an internal helper
routine of Wine, which should not throw any user-visible exception ...
> why don't we just catch the exception as you propose, but then re-raise it
> after switching back to the regular thread's stack ?
If we do want to propagate, it might be easier to use a __FINALLY
block to restore the TEB stack limits if an exception is in fact
unwound across the stack switch ...
(In fact, the caller would need a __FINALLY block as well, to release
the X critical section, otherwise we have an instant deadlock. I really
don't think this is a good idea :-/)
Bye,
Ulrich
--
Dr. Ulrich Weigand
[EMAIL PROTECTED]
