Bug 48987 - SIGABRT in mono-sgen32
Summary: SIGABRT in mono-sgen32
Status: NEW
Alias: None
Product: Runtime
Classification: Mono
Component: General ()
Version: 4.6.0 (C8)
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-12-04 17:18 UTC by moreaki
Modified: 2016-12-05 10:46 UTC (History)
3 users (show)

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

Stack traces (247.61 KB, text/plain)
2016-12-04 17:18 UTC, moreaki

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 48987 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 moreaki 2016-12-04 17:18:46 UTC
Created attachment 18765 [details]
Stack traces

This is probably a very long shot, however I've been trying to compile an extreme legacy software component while trying out the Xamarin Development Ecosystem, to see if by any chance we could move away from a purely Windows-based build system to a MacOSX one.

Anyhow, on my first attempt to simply compile the code, I was greeted with the stack traces I attached due to the size of the output.

Not sure if this is something you guys even have a look at; in any case, I'd be grateful for some pointers.