On Jan 6, 2006, at 1:15 PM, Jean-Francois Im wrote:
This all started when I noticed that an application's windows are
not closed until the CrashReporter's close button is clicked. It
makes sense for most applications to show a dialog instead of just
magically vanishing and leaving a dialog box behind, however, when
the application is a fullscreen window, the CrashReporter actually
appears "behind" the application, with the side effect that the
close button cannot be clicked.
This causes no end of frustration, doesn't it? *sigh*
Simple enough, I thought, it's just a matter of adding a signal
handler, catch the signal for the exceptions, close the window,
then resend the signal to ourself, thus causing the CrashReporter
to pop up. Unfortunately, CrashReporter sets up an exception port,
thus intervening before the signal handler has a chance to do
something(because the exception is not translated into a signal).
/* Set up our signal handlers. */
sa.sa_sigaction = SigHandler;
for( int i = 0; signals[i] != -1; ++i )
sigaction( signals[i], &sa, NULL );
where p is the pointer to our signal stack set up with sigaltstack.
Doing this we can shut down the full screen graphics context and
perform any other clean up. We actually give a stack trace (among
other things) ourself and setting the handlers seems to prevent the
Crash Reporter from running.
Thus, I've searched for information on how to set up an exception
port and have it rethrow the exception after closing the window,
but documentation is quite scarce on the topic of exception ports.
I have found a couple of pointers which sent me on the right track,
but now I appear to have hit a wall.
We didn't have to do anything with exception ports to get this to work.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/darwin-dev/email@hidden
This email sent to email@hidden
