This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
By an accident I have created an exception breakpoint for NullPointerException, AssertionError, AssertionFailedError exceptions and forgot about that. However whenever I debuged my application, it suddenly stopped whenever there was an error in my code. For a while I could not understand why, but then I got it! An error usually means, an exception is raised, and I had my exception breakpoints enabled. I started to like this setup as instead of getting NPE error, the application stopped and I could inspect the values before the exception is thrown and the application continues. This leads me to my suggestion: By default the debugger shall have some exception breakpoints, for well known exceptions enabled. Of course this needs a bit more logic. Very likely I do not care about catched NullPointerExceptions in JDK, etc. But I know there is already filtering for exceptions based on the class they are raised from, so this shall not be big problem.
*** Issue 153972 has been marked as a duplicate of this issue. ***
Planned for 7.0 at http://wiki.netbeans.org/DebuggerExceptionBP70
In addition to well known exceptions consider catching all runtime exceptions. Thanks.
This should work at least in NB 7.1RC2. Just tested by debugging public class Test { public static void main(String[] args) { throw new ArithmeticException("foo"); } } should the bug be marked as resolved?
Thanks.