Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
In some places we just exit for errors, it would be a lot easier to track down these if we aborted instead since it'd generate a crash log (this is of particular importance when a client gets reports from his users - there is no way a user can report a printf back to the client, but an abort will generate a crash log).
See also: http://support.xamarin.com/customer/portal/questions/59501-no-crash-report-generated-when-uncaught-exception
Mono now provides API to install an error callback, and we've added support for that and abort there.