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.

Bug 80837 - Have Method exit breakpoints for exceptional exits
Summary: Have Method exit breakpoints for exceptional exits
Status: NEW
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-21 15:35 UTC by Martin Entlicher
Modified: 2006-10-23 15:46 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Entlicher 2006-07-21 15:35:32 UTC 
When a method is left due to an exception was thrown, method exit breakpoint is
not hit. (This is as designed in JDI.) It's handy, though, to stop execution
when the method is left by any means, including a thrown exception.

To get this to work, one needs to create an Exception breakpoint. This can be
done automatically for the user, as suggested in issue #57442.

It's proposed to add into the Method breakpoint customizer something like:

[X] Stop On Method Exit
    [ ] Add an Exception Breakpoint (Throwable) restricted to this method
[Customize...]
Comment 1 _ sandipchitale 2006-07-21 23:59:50 UTC 
One thing to keep in mind is that Exception breakpoints stop the debugee at 
the location where the exception is thrown.

What I am looking for in the functionality stated in the Summary is that 
stopping on method exit as the stack may be unwinding due to an exception 
thrown in the method that is target of this breakpoint or some method that was 
called from it. I suspect that this needs to be handled/supported by the JVMTI 
itself :(