Bug 41494 - Missing runtime invoke wrappers in leading to many failures in mcs/class tests on mobile_static
Summary: Missing runtime invoke wrappers in leading to many failures in mcs/class test...
Status: RESOLVED FIXED
Alias: None
Product: Runtime
Classification: Mono
Component: JIT ()
Version: 4.5.X
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Alexander Kyte
URL:
Depends on:
Blocks:
 
Reported: 2016-06-03 17:20 UTC by Alexander Kyte
Modified: 2016-06-07 15:38 UTC (History)
3 users (show)

Tags: mobile-static-tests
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:
Status:
RESOLVED FIXED

Description Alexander Kyte 2016-06-03 17:20:06 UTC
This bug is seen using the mobile_static profile with the test MonoTests.System.Reflection.MethodInfoTest.InvokeGenericVtype.

We have this exception:

Unhandled Exception:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ExecutionEngineException: Attempting to JIT compile method '(wrapper runtime-invoke) <Module>:runtime_invoke_KeyValuePair`2<string, uint>_KeyValuePair`2<string, uint> (object,intptr,intptr,intptr)' while running with --aot-only. See http://docs.xamarin.com/ios/about/limitations for more information.

  at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (System.Reflection.MonoMethod,object,object[],System.Exception&)
  at System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) <0x103bfe6a0 + 0x000a9> in <filename unknown>:0
   --- End of inner exception stack trace ---
  at System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) <0x103bfe6a0 + 0x00109> in <filename unknown>:0
  at System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] parameters) <0x103cd6d00 + 0x0002a> in <filename unknown>:0
  at MonoTests.System.Reflection.MethodInfoTest.Main (System.String[] args) <0x1023e1c70 + 0x001ac> in <filename unknown>:0
[ERROR] FATAL UNHANDLED EXCEPTION: Nested exception trying to figure out what went wrong
Comment 1 Alexander Kyte 2016-06-03 18:27:35 UTC
For System.Runtime.Serialization:

https://gist.github.com/alexanderkyte/18f43bed76d2203bad255012d071f8d8
Comment 2 Alexander Kyte 2016-06-03 20:14:29 UTC
It looks like in the first case, we are held up because the call to 
dyn_call_supported by mono_arch_dyn_call_prepare returns NULL because it doesn't yet handle "ArgValuetypeAddrInIReg".
Comment 3 Zoltan Varga 2016-06-06 11:51:29 UTC
That case is now fixed, there might be others.