Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
It looks like mcs does not add the DebuggableAttribute to any assemblies
From what I can see csc automatically adds a DebuggableAttribute as long as /debug is passed. The exact values in the DebuggableAttribute seems to depend on both /debug and /optimize.
$ touch test.cs
$ mcs /target:library test.cs /debug
$ monodis test.dll
And no DebuggableAttribute is found.
That's correct. Why is it needed?
See bug #16898 - customers use this attribute to determine if the assembly was built using a debug or release configuration.
Implemented in master