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.
When running on the Android, when a crash occurs, it does not show filename or line number in the stack trace for the exception.
Does on MonoTouch.
I am also seeing this problem in Android using a Windows development machine.
I also see this with MonoMac. I don't see it with MonoTouch.
To see line numbers in debug mode, you need to set adb shell property as explained here. Try running from command line: adb shell setprop debug.mono.debug 1
How do you know that? The doc pointer you pointed me to does *not* say that.
"debug.mono.debug: If a non-empty string, this is equivalent to `mono --debug`."
Right, that's fair enough: I knew it only because I am also a mono developer. I'd ask our doc team to see if there's better way to explain that. Thanks for the feedback.
How are you launching the app? File + line information should be present within stack traces if you Debug your app from the IDE, e.g. MonoDevelop Run > Start Debugging.
It's only if you launch your app "manually" from the Android Home screen or Run your app (without debugging) that you won't get file + line number information. The reason for this is that `mono --debug` (the equivalent to setting debug.mono.debug) increases memory use and has various other implications.
MonoTouch should be the same, in that `mono --debug` is not the default behavior for all apps, all the time.