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 for Bug 2995 on
Developer Community or GitHub 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
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
The "Custom Command Soft Debugger" option can be enabled with an environment variable MONODEVELOP_SDB_TEST=1, however is not a default option and also makes "Debug" in the Run menu invoke the custom command option.
It would be nice if Debug continues to be the default local soft debugger and that there is an alternate "Debug Custom" option which allows custom command / socket based debugging.
Also with the environment variable set for Custom Command, attempting to run an executable within monodevelop can fail, indicating that is trying to connect to the soft debugger. So something is not quite right in the mode that the environment variable creates.
I that to allow exposing the custom soft debugger we need to use custom execution modes, like Run->Run With->Edit Custom Modes. However, I couldn't find a way to plug it into that without having it show up in the Run With menu by default.