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 36300 on
GitHub or Developer Community 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
Certain JIT intrinsics like Interlocked.Exchange<T> () and Interlocked.CompareExchange<T> () do not emit explicit null checks when this debug option is enabled. This means that on targets that can't turn signals into NREs, these intrinsics won't work correctly in the exceptional case.
Those methods take byref arguments, so its hard for them to be null, at least in c# code.
Nonetheless, it seems we have to do the check for MS.NET compatibility reasons. See this PR: https://github.com/mono/mono/pull/2268