Bug 12683 - Sgen throw unknow exception
Summary: Sgen throw unknow exception
Status: RESOLVED NORESPONSE
Alias: None
Product: Runtime
Classification: Mono
Component: GC ()
Version: unspecified
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-06-13 20:48 UTC by Matteo Fabbri
Modified: 2017-07-07 21:01 UTC (History)
6 users (show)

Tags:
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 NORESPONSE

Description Matteo Fabbri 2013-06-13 20:48:13 UTC
Using mono with --gc=sgen option the application throws on high volume collecting:

Missing or incorrect header for method tem.Runtime.Versioning

No other information are provided.
Comment 1 Matteo Fabbri 2013-06-13 20:49:19 UTC
SO: Ubuntu Server 13 x64
Comment 2 Rodrigo Kumpera 2013-06-17 14:46:40 UTC
This means the runtime could not parse the header of that method, so it's probably missing a dependency or something alike. 

You should try to peverify the assembly that contains it and see if it's working on it. Another option is to write a standard alone program that tried to call it.
Comment 3 Ludovic Henry 2017-07-07 21:01:31 UTC
Can you still reproduce this bug with latest version of mono? Please feel free to reopen if that is still the case. Thank you.