[Mono-bugs] [Bug 642156] New: MonoTools 2.0.8152 with Mono 2.8 rc1 Win XP 32 and openSUSE 11.3 i586: Remote Debug of Winforms app doesn't hit breakpoint

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=642156

https://bugzilla.novell.com/show_bug.cgi?id=642156#c0


           Summary: MonoTools 2.0.8152 with Mono 2.8 rc1 Win XP 32 and
                    openSUSE 11.3 i586: Remote Debug of Winforms app
                    doesn't hit breakpoint
    Classification: Mono
           Product: Mono: Debugger
           Version: unspecified
          Platform: i586
        OS/Version: Windows XP
            Status: NEW
          Severity: Critical
          Priority: P5 - None
         Component: backend
        AssignedTo: martin at novell.com
        ReportedBy: dmulder at novell.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---


Description of Problem:
Debugging a Winforms app remotely hits the break point about 50% of the time.
Sometimes debugging locks up VS, sometimes it simply ignores the breakpoint,
and other times VS crashes and restarts.
Debugging console apps is the same, except that console apps will randomly spit
out "Stop here" to the console instead of hitting the break point.

Steps to reproduce the problem:

   1. Open Visual Studio.
   2. Create a new winforms project.
         1. File
         2. New Project
         3. Visual C#
         4. Windows
         5. Windows Forms Application
         6. Double click on the Form
   3. Add "Console.WriteLine();" to Form1_Load()
   4. Set break point on the Console.WriteLine
   5. [The Linux server should be running.]
   6. Mono->Debug Remotely in Mono


Actual Results:
The break point is not hit and the form never loads.

Expected Results:
The break point should be hit.

How often does this happen? 
About 50% of the time.

Additional Information:

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