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 81226 - ignore bpts on stepover/into
Summary: ignore bpts on stepover/into
Status: VERIFIED DUPLICATE of bug 44582
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-27 08:09 UTC by ivan
Modified: 2006-10-23 16:39 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ivan 2006-07-27 08:09:55 UTC
This is prompted by an nbusers post by twolf@netforensics.com titled
    debugging question: how to stay in same thread when stepping over?

If you have a fair number of breakpoints, when you stepover
or stepinto you might hit the breakpoint. Other than sometimes
being a surprise, if this happens it's very hard to get back to
the original context.

This can happen in multi-threaded situations where some other thread
hits a breakpoint, or non-MT situations where some code you're stepping
over hits your breakpoint.

Ideally one could "nest" interaction with the user such that after
resuming from a bp, which was hit during a step, one gets back to
where they would've ended up at the end of their step.
I know of no debugger that does this.

As a stopgap one could have a flag which controls whether bpts
are ignored during stepping or not. We've had such a flag
in Solaris dbx for quite a while and it seems to have sufficed.
Comment 1 Martin Entlicher 2006-08-14 16:56:11 UTC
We already have issue #44582 for that.
If you use "Continue" action after the breakpoint in another thread was hit, the
step will be finished then and you'll get back to the original context.
We'll try to come up with some good solution in the next version...

*** This issue has been marked as a duplicate of 44582 ***
Comment 2 Jiri Kovalsky 2006-08-14 20:26:04 UTC
Verifying as duplicate of another issue. Thanks for your report anyway !