Please do not reply to this email- if you want to comment on the bug, go to the URL shown below and enter your comments there.
Changed by [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=74869 --- shadow/74869 2006-10-09 20:16:31.000000000 -0400 +++ shadow/74869.tmp.12742 2006-10-10 16:07:42.000000000 -0400 @@ -93,6 +93,24 @@ ------- Additional Comments From [EMAIL PROTECTED] 2006-10-09 20:16 ------- Thanks for this patch Robert, I have applied it to SVN. but we would love to get some feedback from OSX users. + +------- Additional Comments From [EMAIL PROTECTED] 2006-10-10 16:07 ------- +First of all. Great initiative, thanks for looking into this. + +The problem is that when the application really crashes. A sigseg in native code, then it +will not bring up the crashreporter. + +This makes it practically impossible to get crashlogs from end-users because they will +never be printed to the console. We have a fairly large application which sometimes has +bugs and we rely on users being able to send us crashlogs to fix them. + +So for us to be able to use it, the solution would have to differentiate managed null +reference exceptions and native sigsegvs. + +For a managed null referenced exception it should stop the macho exception and continue +running like nothing happened. For a native null reference, it should pass the exception +on, thus causing the crash reporter to popup and print the stacktrace and other debug +info. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
