Bug 14423 - Error: The compiler appears to have crashed. Check the build output pad for details.
Summary: Error: The compiler appears to have crashed. Check the build output pad for d...
Status: RESOLVED NORESPONSE
Alias: None
Product: Compilers
Classification: Mono
Component: C# ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Marek Safar
URL:
Depends on:
Blocks:
 
Reported: 2013-09-04 08:24 UTC by Magnus
Modified: 2013-11-27 05:38 UTC (History)
3 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 Magnus 2013-09-04 08:24:55 UTC
Ive found a bug that causes the compiler to crash with no useful error message.

I accidently wrote something equivalent to this:
                                int ff;
                                ff == 400;

== should have been =

This took me days to find since it just crashed without a clue
Comment 1 Marek Safar 2013-09-04 09:07:44 UTC
I cannot reproduce it. Can you give me more info about the context or run compiler with --mcs-debug 9
Comment 2 Marek Safar 2013-11-27 03:26:44 UTC
No response
Comment 3 Magnus 2013-11-27 05:38:43 UTC
It appears to be fixed now.

It had to be in a InvokeInBackground(()=>{
int ff;
ff == 400;
});

Seems to work now though. Took me days to figure out