Hello, The signal handling was primarly added to help catching message passing to deallocated instance. While this has demonstrated good results in most situation, I have found another way to spot these kind of problems.
So, in the next release, I will make the signal handling optional, so the old behavior will be restored, while keeping the possibility to handle signal exceptions. Regards, Laurent Etiemble. 2009/8/5 Bastien Hofmann <[email protected]>: > Hello, > > In Monobjc 2.0.404.0, it doesn't seem possible to catch > NullReferenceException anymore, instead a SIGBUS signal is intercepted, the > application is stopped with an error message. > > I assume this has something to do with the signal handling added in > 2.0.388.0, however because of this, now instead of having a full callstack > which points me to my null reference, I get an error message and a small > unrelated callstack that doesn't help me find the source of the error. > > Is there a way to restore the previous behavior, or prevent Monobjc from > catching this signal? > > Thanks in advance, > Best regards, > Bastien Hofmann > >
