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
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.
I have installed Monodevelop on two separate systems, one running Ubuntu 10.04 and the other 11.04. I have been unable to enabled integrated debugging on either system. My understanding is that the soft debugger is built in. But the debugging toolbar remains grayed out. I then tried both the MDB and GDB debuggers (and checked add-ins to ensure that they were enabled). The debug tool remains grayed out.
Unfortunately, I cannot find any Monodevelop documentation that tells me what I should expect or how to troubleshoot this issue. There does not seem to be any way to enable this functionality on Ubuntu.
Did you set the active configuration to "x86|Debug"? (replace x86 with whatever arch you are building for)
if it is set to "x86|Release", debugging isn't available.
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?
If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.
Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.