[Mono-bugs] [Bug 606570] New: Cannot view variables, debugger crashes.

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Mon May 17 17:21:24 EDT 2010


http://bugzilla.novell.com/show_bug.cgi?id=606570

http://bugzilla.novell.com/show_bug.cgi?id=606570#c0


           Summary: Cannot view variables, debugger crashes.
    Classification: Mono
           Product: Mono: Debugger
           Version: 2.6.x
          Platform: i686
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: gui
        AssignedTo: martin at novell.com
        ReportedBy: dean.geddes at primus.ca
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---


User-Agent:       Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1;
Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)

When I attempt to view the values of variables the mono debugger crashes.

System.Reflection.TargetInvocationException: Exception has been thrown by the
target of an invocation. ---> System.IO.FileNotFoundException: Could not load
file or assembly 'Mono.Cecil, Version=0.6.9.0, Culture=neutral,
PublicKeyToken=0738eb9f132ed756' or one of its dependencies. The system cannot
find the file specified.

File name: 'Mono.Cecil, Version=0.6.9.0, Culture=neutral,
PublicKeyToken=0738eb9f132ed756'

   at Mono.Debugger.Soft.StackFrame.GetThis()

   at
MonoDevelop.Debugger.Soft.SoftDebuggerAdaptor.GetThisReference(EvaluationContext
ctx)

   at Mono.Debugging.Evaluation.BaseBacktrace.GetFrameInfo(Int32 frameIndex,
EvaluationOptions options, Boolean ignoreEvalStatus)

   at Mono.Debugging.Evaluation.BaseBacktrace.GetLocalVariables(Int32
frameIndex, EvaluationOptions options)

   at Mono.Debugging.Evaluation.BaseBacktrace.GetAllLocals(Int32 frameIndex,
EvaluationOptions options)

   at Mono.Debugging.Client.StackFrame.GetAllLocals(EvaluationOptions options)

   at Mono.Debugging.Client.StackFrame.GetAllLocals()

   at MonoDevelop.Debugger.LocalsPad.OnUpdateList()

   at MonoDevelop.Debugger.ObjectValuePad.<Initialize>b__0(Object , EventArgs )

   at MonoDevelop.Ide.Gui.PadWindow.NotifyContentShown()

   at
MonoDevelop.Ide.Gui.SdiWorkbenchLayout.<>c__DisplayClass9.<AddPad>b__7(Object ,
EventArgs )

   at MonoDevelop.Components.Docking.DockItem.UpdateContentVisibleStatus()

   at MonoDevelop.Components.Docking.DockItem.<SetupContent>b__2(Object ,
ParentSetArgs )



WRN: Assembly binding logging is turned OFF.

To enable assembly bind failure logging, set the registry value
[HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

Note: There is some performance penalty associated with assembly bind failure
logging.

To turn this feature off, remove the registry value
[HKLM\Software\Microsoft\Fusion!EnableLog].



   --- End of inner exception stack trace ---

   at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[]
arguments, SignatureStruct& sig, MethodAttributes methodAttributes,
RuntimeTypeHandle typeOwner)

   at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[]
arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle
typeOwner)

   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean
skipVisibilityChecks)

   at System.Delegate.DynamicInvokeImpl(Object[] args)

   at GLib.Signal.ClosureInvokedCB(Object o, ClosureInvokedArgs args)

   at GLib.SignalClosure.Invoke(ClosureInvokedArgs args)

   at GLib.SignalClosure.MarshalCallback(IntPtr raw_closure, IntPtr return_val,
UInt32 n_param_vals, IntPtr param_values, IntPtr invocation_hint, IntPtr
marshal_data)

MonoDevelop 2.2.2, Mono 2.6.3.

Reproducible: Always

Steps to Reproduce:
1.run a program
2.attempt to view the value of a variable in the local tab
3.
Actual Results:  
debugger dies

Expected Results:  
we see the value of the variable.

-- 
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the mono-bugs mailing list