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

Key: IDEABKL-2517
Type: New Feature New Feature
Status: Open Open
Priority: Normal Normal
Assignee: Unassigned
Reporter: Maxim Shafirov
Votes: 3
Watchers: 2
Available Workflow Actions

Mark as Stalled
Operations

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

Exception Breakpoints: trigger only in user code

Created: 07 Feb 05 20:19   Updated: 11 Apr 07 19:38
Component/s: Debugger
Affects Version/s: None
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown


 Description  « Hide
http://www.intellij.net/tracker/idea/viewSCR?publicId=40276
It would be extremely useful if you could specify that exception breakpoints trigger only in application code. Frequently I turn on breaking for NullPointerException which triggers breaks in JDK and library code.

 All   Comments   Work Log   Change History      Sort Order:
Keith Lea - 26 Mar 06 00:31
The new Visual Studio breaks on every exception thrown, by default. This feature would be unreasonable in IDEA because it would break on exceptions thrown within JDK code, which the developer almost never cares about.

Nathaniel Manista - 11 Apr 07 19:38
To me, an exception is interesting if it is either (1) generated in my project's code or (2) generated in library code and propagated into my project's code. The Exception Breakpoint feature would be much more useful to me if I could select packages (in my case, java., javax., and the subpackages of each) to which I could apply the rule "do not pause execution for exceptions that are both caught and handled entirely in these packages".

If an exception is raised by my project code, I would like the debugger to pause execution immediately. If an exception is raised in library code, it would be acceptable for the debugger to pause execution when exception propagation causes control to be passed from library code to my project's code.

Wouldn't that be awesome? It's worth pointing out that this solution would also solve issue IDEA-12111 (http://www.jetbrains.net/jira/browse/IDEA-12111). At least I think it would. It's hard to tell exactly what that issue is requesting.