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.
This is something that we need to add to MonoDevelop 2.4 for our MonoTouch users.
Currently, when an unhandled exception is being raised, MonoDevelop does nothing with it, and instead just lets the application die.
In MonoTouch this can be replicated by creating a NullReferenceException inside a piece of code, this will end up dumping on the application output window the stack trace, but we never get an exception shown on the IDE stopping the application at the place where the crash took place, allowing us to explore the variables.
While we wait on the updated MonoTouch runtime that can run MonoDevelop/master, we should make sure this is fixed on 2.4
lluis: can you backport the 2.6 fix for this ?
Is it worth backporting this now that we are about to release 2.6?
is this needed anymore?
If i understand correctly MD isn't breaking on unhandled exceptions being throw. Has this been fixed?
We aren't doing any more 2.4.x releases.