[Mono-bugs] [Bug 81557][Maj] New - Exception caused debugger to hang running process
bugzilla-daemon at bugzilla.ximian.com
bugzilla-daemon at bugzilla.ximian.com
Mon May 7 17:21:39 EDT 2007
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=81557
--- shadow/81557 2007-05-07 17:21:39.000000000 -0400
+++ shadow/81557.tmp.6400 2007-05-07 17:21:39.000000000 -0400
@@ -0,0 +1,33 @@
+Bug#: 81557
+Product: Mono: Debugger
+Version: 1.1
+OS:
+OS Details:
+Status: NEW
+Resolution:
+Severity:
+Priority: Major
+Component: cli
+AssignedTo: martin at ximian.com
+ReportedBy: joeshaw at novell.com
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL:
+Cc:
+Summary: Exception caused debugger to hang running process
+
+I'm able to get a lot farther along running Beagle inside the debugger, but
+I'm still hitting a few exceptions that are causing the Beagle process to
+hang after a short while. I'm attaching a log of the Beagle run. There
+are two exceptions.
+
+The first one (System.ArgumentException: Key duplication when adding:
+System.Collections.Generic.EqualityComparer`1) doesn't seem to have any
+effect on the running Beagle process. The process starts up fine.
+
+The second one (EXCEPTION: Mono.Debugger.TargetException: The target is
+currently running, but it must be stopped to perform the requested
+operation.) causes the child process to hang entirely, and nothing happens
+after that. The helper process that beagled starts continues to run, but
+is waiting for messages from the main process and so has nothing to do
+(except log its memory usage every 5 seconds).
More information about the mono-bugs
mailing list