History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: IDEA-12111
Type: Usability Problem Usability Problem
Status: Waiting for Reply Waiting for Reply
Assignee: Eugene Zhuravlev
Reporter: dennis haupt
Votes: 8
Watchers: 7
Operations

If you were logged in you would be able to see more operations.
IDEA: Feedback

Exception Breakpoints are not useful for RuntimeExceptions

Created: 24 Mar 07 15:46   Updated: 27 Mar 07 14:43
Component/s: Debugger

Environment: win2k & xp

Build: 6,776
Severity: High


 Description  « Hide
there is a feature to stop at caught and uncaught exceptions. while useful for own exceptions that are thrown at a few places, the feature isn't useful for most runtimeexceptions like NullPointerException or ClassNotFoundException. In most cases, the exception i'm trying to fix is being thrown in class x at line y. i cannot simply add a break point there because the code is called Z times (z may be really big). it's also impossible to use the exception breakpoint here because it will stop at any exception thrown inside the jre, which is a lot.
stopping only at uncaught exceptions won't help, because almost every exception is caught and wrapped into another in any bigger application, so the break point won't do anything here.

the solution would be to add an exception breakpoint for a specific method, class, package and module.



 All   Comments   Work Log   Change History      Sort Order:
Eugene Zhuravlev - 27 Mar 07 14:42
You can use conditions and class filters - looks like this is what you need. Doesn't it work for you?