Re: enhancing Force Quit or improving user-driven diagnostics
John Hawkinson <jhawk-DPNOqEs/[email protected]> Sun, 15 Jan 2012 13:38:22 -0500
| Newsgroups | gmane.comp.macosx.devel |
|---|---|
| Message-ID | <[email protected]> |
Kevin Reid <kpreid-M/[email protected]> wrote on Sun, 15 Jan 2012 at 12:51:20 -0500 in <67D0ABF4-2770-428A-8F29-E019FF0043C5-M/[email protected]>: > How about setting a signal handler for SIGTERM, the signal Force Quit sends? It's not my app, so it's difficult to install signal handlers. I guess Force Quit sends a SIGTERM before it sends SIGKILL. I am not convinced that the app's signal handling is in good order, and the signal handler would cause some confusion in the stack trace. I would prefer to leave the faulting program's execution environment unaltered by my diagnostics. (Certainly a solution that works for all apps is more along the lines of what I am looking for than a solution that works for just one. But I suppose an LD_PRELOAD -- err, I mean DYLD_INSERT_LIBRARIES -- of a signal handler is a possibility if the more general solution doesn't pan out). THanks. [email protected] John Hawkinson