Bug 2974 - ToString code generation causes fatal error
Summary: ToString code generation causes fatal error
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: 2.8.6
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2012-01-19 17:14 UTC by PJ
Modified: 2012-01-20 11:49 UTC (History)
1 user (show)

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

Log file from crash (2.49 KB, application/octet-stream)
2012-01-19 17:17 UTC, PJ
trace from secondary crash condition (2.21 KB, text/plain)
2012-01-20 11:49 UTC, PJ

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 Developer Community or GitHub 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:

Description PJ 2012-01-19 17:14:29 UTC
Was exploring MonoDevelop feature list. Found http://monodevelop.com/Documentation/Feature_List/Quick_Code_Generation

Decided to run the example.

Upon adding a ToString() implementation, I get a fatal error.


This is on a C# console project, added a new class and pasted in the sample class from the site.

I was on MonoDevelop
Reproduced on 2.8.5 by Lindsey

I will add the stacktrace as an attachment.
Comment 1 PJ 2012-01-19 17:17:07 UTC
Created attachment 1238 [details]
Log file from crash
Comment 2 Mike Krüger 2012-01-20 02:07:35 UTC
Comment 3 PJ 2012-01-20 11:46:57 UTC

I just saw a similar behavior with the 'Equality Members' generation.

The thing is, it only happens (using the exact same example as above) if I select both the int and the string at the same time. Separately generating the code for the int and the string works fine.


Will add new stacktrace as attachment.   I have no idea if the fix you added will fix this issue Mike, so let me know if I should separate this into its own bug and I'll make it happen. Leaving as resolved till I know the actual status.
Comment 4 PJ 2012-01-20 11:49:15 UTC
Created attachment 1244 [details]
trace from secondary crash condition