Bug 45176 - LLVMVerifyModule assert failure in Intel64 AOT Bitcode build
Summary: LLVMVerifyModule assert failure in Intel64 AOT Bitcode build
Status: RESOLVED DUPLICATE of bug 45177
Alias: None
Product: Runtime
Classification: Mono
Component: JIT ()
Version: master
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-10-07 15:06 UTC by Andi McClure
Modified: 2016-10-12 12:49 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Andi McClure 2016-10-07 15:06:49 UTC
For some days now, the nightly Intel64 Bitcode test lane has been failing to build every night:


This has been happening for about a week, starting at about the same time of the big BTLS checkin.

The build happens because of a crash while doing AOT. Sometimes this is while AOTing system.dll:


and sometimes system.net.http.dll:


The failure is this g_assert_not_reached:

		if (LLVMVerifyModule (module->lmodule, LLVMReturnStatusAction, &verifier_err)) {
			printf ("%s\n", verifier_err);
			g_assert_not_reached ();

The verifier_err printf gets swallowed, it does not show up in the console log.
Comment 1 Bernhard Urban 2016-10-12 12:49:28 UTC

*** This bug has been marked as a duplicate of bug 45177 ***