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 for Bug 58209 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
LLVM does not support filter clauses in exception handling, and we fall back to the JIT.
This is a problem on watchOS, where bitcode does not allow us to fall back to the JIT, and at runtime we end up with assertions/exceptions.
I have a POC of a new linker step that detects filter clauses when building for bitcode, and replaces the corresponding method with an exception, and reports a warning at build time: https://github.com/rolfbjarne/xamarin-macios/commit/f1d46b4b1c94fcea92718d1a4d1321f371ed2482 (this POC detects fault clauses as well, since it was implemented before support for fault clauses was implemented in the mono runtime).
This new linker step runs even if the linker is disabled (although that should be a very rare scenario for watchOS apps, since with the linker disabled the app ends up being too big for the App Store).
One major advantage of the linker step is that it makes debug and release builds behave the same (i.e. no surprises when running the release build)