Bug 40519 - symbolication breaks with generic types
Summary: symbolication breaks with generic types
Status: NEW
Alias: None
Product: Tools
Classification: Mono
Component: other ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: marcos.henrich
Depends on:
Reported: 2016-04-19 13:29 UTC by Marek Safar
Modified: 2016-04-19 13:29 UTC (History)
1 user (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 for Bug 40519 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 original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Marek Safar 2016-04-19 13:29:29 UTC
Simple example

using System;
using System.Collections.Generic;

public class M
	public void Foo (List<int> arg)

	public void Foo (List<string> arg)
		int.Parse ("adfa");

class X
	public static void Main ()
		var m = new M ();
		m.Foo (null as List<string>);

The non-aot stacktrace looks like

System.FormatException: Input string was not in a correct format.
  at System.Number.StringToNumber (System.String str, System.Globalization.NumberStyles options, System.Number+NumberBuffer& number, System.Globalization.NumberFormatInfo info, System.Boolean parseDecimal) <0x1ce4bf0 + 0x00124> in <filename unknown>:0 
  at System.Number.ParseInt32 (System.String s, System.Globalization.NumberStyles style, System.Globalization.NumberFormatInfo info) <0x1ce3870 + 0x000ec> in <filename unknown>:0 
  at System.Int32.Parse (System.String s) <0x1cb1200 + 0x0002e> in <filename unknown>:0 
  at M.Foo (System.Collections.Generic.List`1[T] arg) [0x00001] in <filename unknown>:0 
  at X.Main () [0x0000b] in <filename unknown>:0 

The important part is

"  at M.Foo (System.Collections.Generic.List`1[T] arg) [0x00001] in <filename unknown>:0 "

which has List`1[T] which is not enough to determine correct overload.

Note: When I was looking into it I noticed we expand the generic argument in complex cases only, e.g. IEnumerable<int[,,,][]> which is probably different bug.