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.
Created attachment 14825 [details]
Picture showing debugger being indicated not attached
Android.OS.Debug.IsDebuggerConnected returns false even though the Xamarin/Mono debugger is attached. This is confusing and counter intuitive, and isn't mentioned in the documentation.
Can this method either be fixed, or can the documentation be updated to reflect the true nature of the property please?
I also posted this on StackOverflow: http://stackoverflow.com/questions/35090054/xamarin-isdebuggerconnected-returns-incorrect-value
A (the?) problem is that there are *at least three* possible debuggers running around, and none know about the others:
1. The Java debugger, which is what android.os.Debug.isDebuggerConnected() knows about.
2. The Mono debugger (sdb), which System.Diagnostics.Debugger.IsAttached knows about.
3. gdb or any other native debugger (such as lldb), which *nothing* knows about.
We do not plan on updating Android.OS.Debug.IsDebuggerConnected to be aware of the mono debugger.
We will look into updating the documentation.