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 59915 - Cannot add breakpoints when debugging another project
Summary: Cannot add breakpoints when debugging another project
Status: VERIFIED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Martin Entlicher
URL:
Keywords:
: 58585 82497 106345 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-06-14 08:36 UTC by Jiri Prox
Modified: 2007-06-12 09:34 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 Jiri Prox 2005-06-14 08:36:06 UTC
NB 4.1 fcs
JDK 1.5.0_03

The breakpoints cannot be added to the ant script when another debugger is
running (the ant debugger is not running, otherwise it works)
When runs ant debugger breakpoints cannot be added to others projects.

Steps:
1) open project base on existing antscript
2) open normal project
3) start debugger on ant script project
4) try to add breakpoint somewhere in the normal project
-> doesn't work
5) stop the ant debuger
6) place breakpoint in normal project and run its debugger (it should stop on
breakpoint)
7) try to add breakpoint to ant script project
-> doesn't work
Comment 1 Martin Entlicher 2005-12-09 11:25:18 UTC
Reproduced. Starting to work on it...
Comment 2 Martin Entlicher 2005-12-09 14:08:46 UTC
This is a problem in debugger core.
The ActionsManager does not have the AntBreakpointActionProvider registered when
JPDA debugger is started. Only JPDA-related providers are used. Therefore the
Toggle Breakpoint action is not enabled on ant files.
The same, but vice-versa happens when ant debugger is started.
Comment 3 Martin Entlicher 2005-12-09 14:11:41 UTC
*** Issue 58585 has been marked as a duplicate of this issue. ***
Comment 4 Martin Entlicher 2005-12-09 14:35:18 UTC
This likely needs some change in the architecture - too late for 5.0. Scheduling
for future...
Comment 5 Jonelle Almero 2006-09-19 18:17:33 UTC
*** Issue 82497 has been marked as a duplicate of this issue. ***
Comment 6 Michael Frisino 2006-09-19 19:02:41 UTC
We should document this issue in Trouble shooting section of BPEL Design guide.
Comment 7 Michael Frisino 2006-09-19 19:03:14 UTC
sorry meant to add that comment to the BPEL duplicate of this bug.
Comment 8 artibee 2006-09-20 17:25:45 UTC
What is the workaround? 
Comment 9 Martin Entlicher 2006-09-20 17:57:55 UTC
The workaround is to wait with the setting of breakpoints till the appropriate
debugger session is started (or made active), or finish the current debugging
session.
In other words, while e.g. Java debugger is active, no BPEL or ANT breakpoint
can be submitted. So either Java session needs to be finished, or BPEL or ANT
debugger started (there can be several sessions running simultaneously, but only
one can be active).
Comment 10 Martin Entlicher 2006-09-20 17:58:25 UTC
Fixed in trunk, hopefully without undesired side-effects.

The actions from the default actions manager are taken into account when they
are not enabled in the current engine's actions manager.
This makes breakpoint actions providers work also in non-active debuggers.

/cvs/debuggercore/src/org/netbeans/modules/debugger/ui/actions/DebuggerAction.java,v
 <--  DebuggerAction.java
new revision: 1.13; previous revision: 1.12
Comment 11 Martin Entlicher 2006-09-20 18:03:47 UTC
I've merged the fix into release55_dev branch, so that you can test it and
decide whether we should integrate this fix into release55.

/shared/data/ccvs/repository/debuggercore/src/org/netbeans/modules/debugger/ui/actions/DebuggerAction.java,v
 <--  DebuggerAction.java
new revision: 1.8.8.2.2.1.14.1; previous revision: 1.8.8.2.2.1

Comment 12 Jiri Prox 2006-12-14 10:05:03 UTC
verified in trunk
Comment 13 Martin Entlicher 2007-06-12 09:34:18 UTC
*** Issue 106345 has been marked as a duplicate of this issue. ***