[Mono-bugs] [Bug 447663] Debugger stops on NullRefException

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Fri Nov 21 13:30:48 EST 2008


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

User martin at novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=447663#c1


Martin Baulig <martin at novell.com> changed:

           What    |Removed                                         |Added
----------------------------------------------------------------------------
             Status|NEW                                             |RESOLVED
         Resolution|                                                |FEATURE




--- Comment #1 from Martin Baulig <martin at novell.com>  2008-11-21 11:30:47 MST ---
Well, this is not a bug, this is a feature.  A debugger clearly has to stop on
each signal it receives.

What's missing is an API which let's you (the GUI) control which signals should
cause a stop, and which signals should be passed to the target etc. - like gdb
does with its `handle' command.

I need something similar for VS, so I'll add such an API soon.

If SIGSEGV is the only signal you care about, I'll add a quick fix to
GUIManager.cs.


-- 
Configure bugmail: https://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