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 43002 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
We use mono_get_runtime_build_info to ensure our system mono and the XM mono are in sync. This runtime function returns the version of the runtime and from what source it's built.
Released system mono builds report the branch and commit hash, but the mono build shipped with XM reports "tarball".
As such, it's not possible to tell what Mono bump ever made it into an XM build, which I was hoping to use to verify a bump for my own sanity.
mono_get_runtime_build_info returns the version line that you would see from "mono --version" (but XM doesn't ship the mono driver, so we make the runtime call instead).