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
GitHub or Developer Community 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 1135 [details]
If you hover over a DateTime while debugging to get the tooltip, the tooltip shows Chinese(?) characters instead of the DateTime.
This occurs in both VS and MD, so I am guessing it is in the MD debugging libraries.
However, it only occurs when debugging MFA projects:
haha, that is awesome.
Unfortunately, I'm not able to reproduce this. What is your debugger configuration?
MonoDevelop -> Preferences -> Debugger
Are you using the Soft debugger or some other debugger?
Aha, only for Mono for Android. I guess I'll need to install M4A
Actually, if this is a bug in both VS *and* MD when debugging M4A, doesn't that suggest an M4A bug?
My guess is it can either be a debugging library issue or a runtime issue.
Can you test MT?
Works fine in MonoTouch.
Reproducible in MD/Mac/MFA
Did more digging...
The Soft debugger backend in MD is invoking ToString() on the DateTime struct in Mono.Debugging.Soft.SoftDebuggerAdaptor.CallToString() and getting back a StringMirror with garbage, apparently.
This is either a bug in the runtime or a bug in M4A somewhere.
The debugger module in the runtime receives the garbage string as the result of
mono_runtime_invoke () at debugger-agent.c:5479. The input struct appears to be valid. Calling ToString() directly from the app also appears to work.
Added a workaround to mobile-master in a98b00fece7e44962d2324bfb9a63744bc68d8cb.
Fixed in HEAD/2.10.
*** Bug 3837 has been marked as a duplicate of this bug. ***