Le 27 janv. 09 à 06:03, Slava Pestov a écrit :
On Mon, Jan 26, 2009 at 10:43 PM, Michael Ash
michael@gmail.com wrote:
Actually it's pretty easy to avoid exiting due to EXC_BAD_ACCESS,
just
install a signal handler for SIGSEGV.
In my experience, setting a handler for SIGSEGV is
Le 27 janv. 09 à 06:48, Bill Bumgarner a écrit :
On Jan 26, 2009, at 8:43 PM, Michael Ash wrote:
Actually it's pretty easy to avoid exiting due to EXC_BAD_ACCESS,
just
install a signal handler for SIGSEGV.
Of course, doing something rational in such a signal handler is ever
so slightly
On Jan 27, 2009, at 12:57 AM, Jean-Daniel Dupas wrote:
If you want, I have a proof of concept that catch exception like
EXC_BAD_ACCESS, and skip the faulting instruction (by incrementing
the program counter registry) to continue programme execution.
No need to say I did it only for
For the beta-testing purposes, I'd like my app to handle the situation
when the EXC_BAD_ACCESS exception occurs, and treat it gracefully -
i.e. send a crash report and perhaps terminate.
Currently, the app just hangs and needs the user to send Force Quit to
terminate the app.
I tried to wrap the
On 26 Jan 2009, at 11:33, Oleg Krupnov wrote:
For the beta-testing purposes, I'd like my app to handle the situation
when the EXC_BAD_ACCESS exception occurs, and treat it gracefully -
i.e. send a crash report and perhaps terminate.
Currently, the app just hangs and needs the user to send
Currently, the app just hangs and needs the user to send Force Quit to
terminate the app.
You sure about that? It can take a while to prepare the crash report, and
during that time your app is certainly non-responsive. But that signal
causes the system to terminate your application, and I have
On Mon, Jan 26, 2009 at 7:16 AM, jonat...@mugginsoft.com
jonat...@mugginsoft.com wrote:
EXC_BAD_ACCESS is not an application exception it is a Unix signal.
Signals are a BIG topic.
EXC_BAD_ACCESS is not a UNIX signal, it is a Mach exception. In
response to this exception, the UNIX layer will
On Mon, Jan 26, 2009 at 12:09 PM, Scott Ribe scott_r...@killerbytes.com wrote:
Currently, the app just hangs and needs the user to send Force Quit to
terminate the app.
You sure about that? It can take a while to prepare the crash report, and
during that time your app is certainly
On Mon, Jan 26, 2009 at 10:43 PM, Michael Ash michael@gmail.com wrote:
Actually it's pretty easy to avoid exiting due to EXC_BAD_ACCESS, just
install a signal handler for SIGSEGV.
In my experience, setting a handler for SIGSEGV is problematic because
the crash reporter still starts up, so
On Jan 26, 2009, at 8:43 PM, Michael Ash wrote:
Actually it's pretty easy to avoid exiting due to EXC_BAD_ACCESS, just
install a signal handler for SIGSEGV.
Of course, doing something rational in such a signal handler is ever
so slightly non-trivial.
Hahahaha yeah. That is an
10 matches
Mail list logo
