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
GitHub or Developer Community 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.
ive stumbled upon this yesterday in my project.
here is a working minimal example https://pastebin.com/SxGNDNia
here is the output of mono -V
Mono JIT compiler version 188.8.131.52 (tarball Wed Nov 8 20:37:08 UTC 2017)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
LLVM: supported, not enabled.
GC: sgen (concurrent by default)
(didnt know if i shouldve selected 5.4 in the above version selector, but it didnt fit the date)
im on ubuntu 16.04
in the example i deliberately create a stackoverflow exception (like it accidentally happened in my codebase). in the outer try catch i then catch an exception, which is null. i would either expect a stackoverflowexception instance, or the same behaviour as .net framework (the code will let the runtime abort the process on windows).
the example code bit is part of a visual studio solution (vs 2017) (i can also provide the whole project if needed)
i compiled the solution on linux using msbuild (cd into solution dir, call msbuild)
then i ran the exe with mono --debug <exe name>
instead of the program continuing to run, and telling me there was a fault detected, i would expect some message like "process was aborted due to stack overflow", just like .net framework does. (personally i would prefer it to throw the exception so i can log it, but framework doesnt do it either).
Created attachment 25841 [details]
I can reproduce with Mono 184.108.40.206 (2017-10/efce3b256a5).
It doesn't behave like a typical stack overflow exception where there is nested stack overflow, and it actually behaves quite decently, so I don't really know why we get a `ex = null` at the end.
Zoltan, would you mind taking a look at this one?