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 52535 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
In this forum thread:
A XM user would like to use Assembly.Load(byte) to load an assembly while still consuming the AOT they generated before.
In theory, they could use mono_aot_register_module before loading the assembly, except for one problem. We do not emit the mono_aot_module_ symbol in dylibs, just static libs.
We emit a 'mono_aot_file_info' symbol instead, you can use dlopen()+dlsym() to find it.
@Zoltan - We tried mono_aot_file_info - See crash here - https://forums.xamarin.com/discussion/comment/253104/#Comment_253104
Try aot-ing the image using the 'static' option, i.e.:
mono --aot=static foo.dll