[F-Script-talk] Re: Handle prematurely deallocated objects?

[Philippe M. <pm...@ac...>]

The current F-Script code already try to handle this situation=20
gracefully (although, as you point out, this does not work!). In the=20
current code, we use Apple's NSExceptionHandler class to set an=20
exceptionHandling mask to 63, which, according to Cocoa's doc should=20
raise an exception when a error like bad memory access happen. But=20
instead, F-Script hangs (it seems to be stuck in the=20
NSExceptionHandlerUncaughtSignalHandler() system function, which seems=20=

to be called by a signal handler).

Best,

Phil

Le mercredi, 11 jun 2003, =E0 08:34 Europe/Paris, Nicholas Seckar a =
=E9crit=20
:

> 	I've noticed that F-Script crashes when it tries to access a=20
> prematurely deallocated object. The crash is not a 'clean' failure, as=20=

> F-Script simply hangs until I kill it.
> 	While this isn't overly important, it would still be nicer to =
see=20
> this fixed. As usual, GDB logs EXC_BAD_ACCESS when this occurs. Anyone=20=

> want to write a signal handler?
>