Bug 1751 - Abort instead of exit
Summary: Abort instead of exit
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 4.x
Hardware: PC Windows
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2011-10-28 05:29 UTC by Rolf Bjarne Kvinge [MSFT]
Modified: 2015-04-16 14:16 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Rolf Bjarne Kvinge [MSFT] 2011-10-28 05:29:31 UTC
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
Comment 1 Rolf Bjarne Kvinge [MSFT] 2015-04-16 14:16:49 UTC
Mono now provides API to install an error callback, and we've added support for that and abort there.

maccore: bdd4f092bc2040bdad604845fedb8a641405b065