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.
Error in soft debugger method call thread on method Boolean System.Threading.CancellationToken:get_IsCancellationRequested () on object System.Threading.CancellationToken
System.InvalidOperationException: The vm is not suspended.
at Mono.Debugger.Soft.VirtualMachine.ErrorHandler (System.Object sender, Mono.Debugger.Soft.ErrorHandlerEventArgs args) [0x0004f] in /home/marek/git/monodevelop/main/contrib/Mono.Debugger.Soft/Mono.Debugger.Soft/VirtualMachine.cs:287
at Mono.Debugger.Soft.ObjectMirror.EndInvokeMethodInternal (IAsyncResult asyncResult) [0x0004a] in /home/marek/git/monodevelop/main/contrib/Mono.Debugger.Soft/Mono.Debugger.Soft/ObjectMirror.cs:259
at Mono.Debugger.Soft.StructMirror.EndInvokeMethod (IAsyncResult asyncResult) [0x00001] in /home/marek/git/monodevelop/main/contrib/Mono.Debugger.Soft/Mono.Debugger.Soft/StructMirror.cs:68
at Mono.Debugging.Soft.MethodCall.EndInvoke () [0x00074] in /home/marek/git/monodevelop/main/src/addins/MonoDevelop.Debugger.Soft/Mono.Debugging.Soft/SoftDebuggerAdaptor.cs:1275
Mono.Debugging.Evaluation.EvaluatorException: The vm is not suspended.
at Mono.Debugging.Soft.MethodCall.get_ReturnValue () [0x0002f] in /home/marek/git/monodevelop/main/src/addins/MonoDevelop.Debugger.Soft/Mono.Debugging.Soft/SoftDebuggerAdaptor.cs:1336
at Mono.Debugging.Soft.SoftEvaluationContext.RuntimeInvoke (Mono.Debugger.Soft.MethodMirror method, System.Object target, Mono.Debugger.Soft.Value values) [0x0012a] in /home/marek/git/monodevelop/main/src/addins/MonoDevelop.Debugger.Soft/Mono.Debugging.Soft/SoftEvaluationContext.cs:134
at Mono.Debugging.Soft.PropertyValueReference.get_Value () [0x00018] in /home/marek/git/monodevelop/main/src/addins/MonoDevelop.Debugger.Soft/Mono.Debugging.Soft/PropertyValueReference.cs:98
at Mono.Debugging.Evaluation.ObjectValueAdaptor.EvaluateDisplayString (Mono.Debugging.Evaluation.EvaluationContext ctx, System.Object obj, System.String exp) [0x000ba] in /home/marek/git/monodevelop/main/src/core/Mono.Debugging/Mono.Debugging.Evaluation/ObjectValueAdaptor.cs:1003
at Mono.Debugging.Evaluation.ObjectValueAdaptor.CreateObjectValueImpl (Mono.Debugging.Evaluation.EvaluationContext ctx, IObjectValueSource source, ObjectPath path, System.Object obj, ObjectValueFlags flags) [0x000ef] in /home/marek/git/monodevelop/main/src/core/Mono.Debugging/Mono.Debugging.Evaluation/ObjectValueAdaptor.cs:345
at Mono.Debugging.Evaluation.ObjectValueAdaptor.CreateObjectValue (Mono.Debugging.Evaluation.EvaluationContext ctx, IObjectValueSource source, ObjectPath path, System.Object obj, ObjectValueFlags flags) [0x00002] in /home/marek/git/monodevelop/main/src/core/Mono.Debugging/Mono.Debugging.Evaluation/ObjectValueAdaptor.cs:66
This happens frequently when switching between threads
Created attachment 1735 [details]
Occasionally crashes mono but mostly causes debugger to return bogus values
I also frequently get this and when trying to step. Something happens and the debugger thinks it has not been suspended but the application never progresses. I haven't figured out a good repro for it
Someone's going to have to create a test case I can actually use (I don't seem to have libintl.dylib so marek's test case won't run for me).
I tried creating a simple multi-threaded app but I can't reproduce this issue.
I'm seeing this in VS 2012 on Android. It makes it impossible to debug.
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?
If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.
Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.