[Mono-bugs] [Bug 530596] New: Creating a new breakpoint while debugging causes old break points to get hit again

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Wed Aug 12 19:31:29 EDT 2009


           Summary: Creating a new breakpoint while debugging causes old
                    break points to get hit again
    Classification: Mono
           Product: Mono: Tools
           Version: MonoVS 0.3
          Platform: i586
        OS/Version: Windows XP
            Status: NEW
          Severity: Major
          Priority: P5 - None
         Component: Visual Studio Integration
        AssignedTo: martin at novell.com
        ReportedBy: twiest at novell.com
         QAContact: mono-bugs at lists.ximian.com
                CC: jpobst at novell.com
          Found By: Component Test

Description of Problem:
If you create a new break point while you're debugging an application, an
already hit break point will incorrectly get hit again (see the steps to
reproduce, it's kinda hard to explain).

This was found in MonoVS 0.3p3.

Steps to reproduce:
1) Create a new solution based on the C# console project template
2) Add these lines to Main:
3) Add a break point to the 1st Console.WriteLine()
4) Click "Mono / Debug Remotely in Mono"
5) Wait for the debugger to stop on the 1st break point
6) Add a break point to the 2nd Console.WriteLine()
7) Click "Debug / Continue"
8) Notice that the debugger doesn't move off of the 1st Console.WriteLine()
9) Click it again
10) Notice that this time it does move to the 2nd Console.WriteLine()

If you do the same steps as above without adding a break point, then it does
not re-break on the 1st Console.WriteLine().

Actual Results:
It re-breaks on the 1st Console.WriteLine()

Expected Results:
It should continue.

How often does this happen? 
every time.

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