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
