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 175475 - Per project breakpoints
Summary: Per project breakpoints
Status: RESOLVED FIXED
Alias: None
Product: cnd
Classification: Unclassified
Component: Debugger (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Egor Ushakov
URL:
Keywords:
: 210312 222246 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-10-26 23:43 UTC by tbrunhoff
Modified: 2012-11-26 11:46 UTC (History)
2 users (show)

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 tbrunhoff 2009-10-26 23:43:47 UTC
If you open window-->debugging-> breakpoints, the list of breakpoints may include files from multiple projects, which
cannot easily be identified. It may even include breakpoints in files from projects that are no longer open in the ide.
For me, here's how I got to this point (I think):
 - open project A
 - open a file in project A, set a breakpoint
 - open project B
 - open a file in project B, set a breakpoint (most interesting if the file has the same name as in project A)
The breakpoints window shows breakpoints that mention only the file and line number, not the project. Seems like there
should be a project column. And/Or that the current project is easily identifiable. Now...
 - close project A
The breakpoints window still shows breakpoints in project A files.
Comment 1 Egor Ushakov 2009-10-27 10:51:57 UTC
This is a general Netbeans infrastructure problem :(
Breakpoints are not per project but global.
Comment 2 pekarna 2011-02-22 23:45:17 UTC
I've a similar RFE, a bit broader:

 Bug 188551 -  RFE: Slight enhancement of HTML editing  (edit)
Comment 3 ivan 2011-11-04 21:36:42 UTC
See also CR 7107992.
The scenario there is a project was deleted but the line breakpoints for
files in that project are still around.
Comment 4 tbrunhoff 2012-04-18 18:43:06 UTC
Bug 210312 shows what can happen when you *don't* have per-project breakpoints.
Comment 5 igor_nikiforov 2012-04-19 10:43:43 UTC
*** Bug 210312 has been marked as a duplicate of this bug. ***
Comment 6 tbrunhoff 2012-11-07 19:40:08 UTC
This is still broken after 2 years. I'd propose that since NB (a) supports multiple projects, and (b) as an ide debugging is a crucial part, (c) breakpoints are not recorded on a per-project basis, which causes (d) various problems listed below.... therefore this bug is a defect.
Comment 7 Leonid Lenyashin 2012-11-07 19:52:21 UTC
Please evaluate, looks like must be transfered to NB debugger
Comment 8 Egor Ushakov 2012-11-08 09:58:58 UTC
For java there is a notion of breakpoint groups and filtering per project and for opened projects only. This is implemented in general debugging infrastructure and only needs to be supported.
Comment 9 Egor Ushakov 2012-11-08 14:44:29 UTC
fixed in:
http://hg.netbeans.org/cnd-main/rev/2756a226ed37
I've enabled breakpoint groups for cnd.
Now there is a button in the breakpoints view where you can select how you want to group the breakpoints (you can group by project) and also specify that you do not need to see breakpoints from closed projects.
Currently only line breakpoints "know" their project.
Please try it when available in dev build and say if it solves the problem.
Comment 10 Quality Engineering 2012-11-09 02:52:34 UTC
Integrated into 'main-golden', will be available in build *201211090001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main-golden/rev/2756a226ed37
User: Egor Ushakov <gorrus@netbeans.org>
Log: fixed #175475 - Per project breakpoints
Comment 11 Alexander Pepin 2012-11-09 14:13:02 UTC
Per-project breakpoints should be covered by automatic tests.
Comment 12 henk89 2012-11-26 11:46:27 UTC
*** Bug 222246 has been marked as a duplicate of this bug. ***