[Mono-bugs] [Bug 77056][Maj] Changed - resuming "next" after non-breaking breakpoint

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Thu Jan 19 05:53:18 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 martin at ximian.com.

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

--- shadow/77056	2005-12-21 16:11:25.000000000 -0500
+++ shadow/77056.tmp.29380	2006-01-19 05:53:18.000000000 -0500
@@ -3,21 +3,21 @@
 Version: 1.1
 OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
 Severity: Unknown
-Priority: Normal
+Priority: Major
 Component: cli
 AssignedTo: martin at ximian.com                            
 ReportedBy: joeshaw at novell.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 URL: 
 Cc: 
-Summary: When mdb files are missing, doing "next" goes into "instruction" mode
+Summary: resuming "next" after non-breaking breakpoint
 
 If you're stepping through a program with "next", and you encounter a line
 in an assembly with no debugging information, mdb goes into an
 "instruction" mode.  I'm not really interested in stepping through the
 instructions, I would rather it just execute the line like gdb does. 
 "next" should execute lines and return to the current stack frame (unless a


More information about the mono-bugs mailing list