Bug 17673 - AOT compiler segfaults when receiving wildcards as argument
Summary: AOT compiler segfaults when receiving wildcards as argument
Alias: None
Product: Runtime
Classification: Mono
Component: AOT ()
Version: unspecified
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2014-02-09 17:36 UTC by Andres G. Aragoneses
Modified: 2018-01-24 17:03 UTC (History)
5 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 Andres G. Aragoneses 2014-02-09 17:36:07 UTC
mono --aot Foo.dll works perfectly, but:

mono --aot *.dll breaks badly:

* Assertion at class.c:5597, condition `!mono_loader_get_last_error ()' not met


Native stacktrace:

	mono() [0x80fd6d3]
	/lib/i386-linux-gnu/libc.so.6(gsignal+0x4f) [0xb75201df]
	/lib/i386-linux-gnu/libc.so.6(abort+0x175) [0xb7523825]
	mono() [0x8283380]
	mono() [0x8283403]
	mono() [0x815f010]
	mono(mono_class_get_full+0x127) [0x8160367]
	mono(mono_class_get+0x1f) [0x81604af]
	mono(mono_class_from_name+0xff) [0x81605bf]
	mono(mono_class_from_typeref+0x12b) [0x815fe6b]
	mono(mono_class_get_full+0x18c) [0x81603cc]
	mono() [0x815f160]
	mono(mono_class_get_full+0x127) [0x8160367]
	mono(mono_class_get+0x1f) [0x81604af]
	mono(mono_class_from_name+0xff) [0x81605bf]
	mono(mono_class_from_typeref+0x12b) [0x815fe6b]
	mono() [0x8188fd6]
	mono() [0x8189538]
	mono(mono_get_method_full+0xa4) [0x8189764]
	mono(mono_get_method+0x27) [0x81898e7]
	mono() [0x80e0adf]
	mono() [0x80e14d5]
	mono() [0x80e3b3e]
	mono(mono_main+0x127a) [0x80d0faa]
	mono() [0x805d58c]
	/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0xb750b4d3]
	mono() [0x805d721]

Debug info from gdb:

Could not attach to process.  If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf
ptrace: Operation not permitted.
No threads.

Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.

Aborted (core dumped)

This is with mono master and 3.2.7 branch.
Comment 1 Miguel de Icaza [MSFT] 2014-02-11 12:28:57 UTC
That is not really a problem with wildcards, since mono itself never receives a wildcard.

The above is a crash in a specific assembly.   So we do need to identify which assembly is causing this crash.
Comment 2 Ludovic Henry 2017-09-26 14:59:23 UTC

Can you still reproduce with latest mono? If so, could you please provide the assembly on which it is crashing?

Thank you
Comment 3 Ludovic Henry 2018-01-24 17:03:49 UTC
Please provide information requested in previous comment to reopen. Thank you.