On Apr 7, 2011, at 10:02 AM, Jeremy Huddleston wrote:

> 
> On Apr 7, 2011, at 9:41 AM, Pelle Johansson wrote:
> 
>> Is the function named signal_handler part of quartz-wm? Because it should be 
>> calling _exit, not exit. Though that's just a followup bug I suppose.
> 
> Ah, good call.  That is our handler.  That still doesn't explain:
> 
> 1) Why are we in x_init_error_handler while in CFRunLoop?
> 2) Why did ImageLoaderMachO::doTermination barf?
> 
> As for us moving over to _exit(2) or _Exit(3) rather than exit(3), that would 
> fix one of the problems, that's actually one of the least offensive of the 
> signal_handler's crimes.  It looks like we're calling some *very* 
> non-reentrant routines from within the SIGINT and SIGTERM signal handler, 
> such as various calls into Xlib to make the window state safe for us to exit. 
>  Yuck!  At least SIGHUP (for reloading preferences) is safe.

Ok, well I have a fix for the reentrancy snafu.  It'll be in 2.6.2_beta1 
(probably tomorrow or early next week).

--Jeremy


_______________________________________________
Xquartz-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev

Reply via email to