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.
1) Keep executing the 'Step Into' command while debuggin
2) For every class you step into which does not have source code you get this:
WARNING [2012-03-21 17:10:16Z]: Debugger could not find file '/private/tmp/monobuild/build/BUILD/mono-2.10.9/mcs/class/System.XML/System.Xml/XmlTextReader2.cs'
WARNING [2012-03-21 17:10:17Z]: Debugger could not find file '/private/tmp/monobuild/build/BUILD/mono-2.10.9/mcs/class/System.XML/System.Xml/XmlTextReader.cs'
WARNING [2012-03-21 17:10:17Z]: Debugger could not find file '/private/tmp/monobuild/build/BUILD/mono-2.10.9/mcs/class/System.XML/System.Xml/XmlTextReader2.cs'
and the debugger looks like it has hung as it does not advance. The default behaviour should be to keep advancing until the debugger finds the next instruction with available source code.
There could be an alternative mode which opens the disassembly view and steps through the actual IL instructions. For example in the screenshot here ( http://screencast.com/t/evl03ZEm7 ) I would expect that if i choose 'step into' while the debugger was on the while loop, it would immediately step to data.SkeipNextRead = false as there is no debug info available for XmlReader.
I don't think that's a good solution. You're basically hiding an error - that you have mdb files but not the source files they point to.
Step Into already steps though non-user code, unless you have debugging of non-user code enabled, so this isn't likely to affect most users. If you have source files missing for your user code, something is seriously wrong.
If you're debugging non-user code, chances are you do want to step into the code - that's why it steps into the disassembly view if it doesn't have symbols. If it has symbols but didn't find the source files, we could prompt for the file, or maybe even use a source server - but that fails, we should open the disassembly view.
I do have project-only debugging enabled (which is the default). As such, MonoDevelop should never have tried to step into the XmlReader code. I will file a separate bug for this.
As for handling the situation where there are mdb files and no source, the best option sounds like it would be to use the disassembly view for now.
pretty sure this has been fixed