[Mono-bugs] [Bug 77567][Nor] New - Attaching to processes throws an exception

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Wed Feb 15 14:53:51 EST 2006


Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by joeshaw at novell.com.

http://bugzilla.ximian.com/show_bug.cgi?id=77567

--- shadow/77567	2006-02-15 14:53:51.000000000 -0500
+++ shadow/77567.tmp.25668	2006-02-15 14:53:51.000000000 -0500
@@ -0,0 +1,70 @@
+Bug#: 77567
+Product: Mono: Debugger
+Version: 1.1
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: cli
+AssignedTo: martin at ximian.com                            
+ReportedBy: joeshaw at novell.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Attaching to processes throws an exception
+
+From svn, r56748.  This is probably related to 77566.  They seem to have
+the same stack trace.
+
+Start a mono app, and then run mdb separately.
+
+Load the executable file with the "file" command:
+
+(mdb) file /home/joe/cvs/beagle/tools/Settings.exe
+Executable file: /home/joe/cvs/beagle/tools/Settings.exe.
+
+And then try to attach to the running process:
+
+(mdb) attach 9244
+Attaching to 9244
+ERROR: Caught exception while executing command
+Mono.Debugger.Frontend.AttachCommand: System.ArgumentException: An invalid
+argument was specified.
+
+Server stack trace:
+in [0x0009b] (at /home/joe/cvs/mcs/class/corlib/System.IO/Path.cs:167)
+System.IO.Path:GetDirectoryName (System.String path)
+in [0x00159] (at /home/joe/cvs/debugger/backends/ProcessStart.cs:105)
+Mono.Debugger.Backends.ProcessStart:.ctor (Mono.Debugger.DebuggerOptions
+options)
+in [0x00002] (at /home/joe/cvs/debugger/backends/ProcessStart.cs:111)
+Mono.Debugger.Backends.ProcessStart:.ctor (Mono.Debugger.DebuggerOptions
+options, Int32 pid)
+in (wrapper remoting-invoke-with-check)
+Mono.Debugger.Backends.ProcessStart:.ctor (Mono.Debugger.DebuggerOptions,int)
+in [0x00020] (at /home/joe/cvs/debugger/backends/Debugger.cs:136)
+Mono.Debugger.Debugger:Attach (Mono.Debugger.DebuggerOptions options, Int32
+pid)
+in (wrapper remoting-invoke-with-check) Mono.Debugger.Debugger:Attach
+(Mono.Debugger.DebuggerOptions,int)
+in (wrapper xdomain-dispatch) Mono.Debugger.Debugger:Attach
+(object,byte[]&,byte[]&,int)
+
+Exception rethrown at [0]:
+
+in (wrapper xdomain-invoke) Mono.Debugger.Debugger:Attach
+(Mono.Debugger.DebuggerOptions,int)
+in (wrapper remoting-invoke-with-check) Mono.Debugger.Debugger:Attach
+(Mono.Debugger.DebuggerOptions,int)
+in <0x000f5> Mono.Debugger.Frontend.Interpreter:Attach (Int32 pid)
+in (wrapper remoting-invoke-with-check)
+Mono.Debugger.Frontend.Interpreter:Attach (int)
+in <0x0004d> Mono.Debugger.Frontend.AttachCommand:DoExecute
+(Mono.Debugger.Frontend.ScriptingContext context)
+in <0x0001f> Mono.Debugger.Frontend.DebuggerCommand:Execute
+(Mono.Debugger.Frontend.ScriptingContext context)
+in <0x00096> Mono.Debugger.Frontend.DebuggerCommand:Execute
+(Mono.Debugger.Frontend.Engine e)


More information about the mono-bugs mailing list