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 49242 - [40cat] Session not made current when reaching a breakpoint.
Summary: [40cat] Session not made current when reaching a breakpoint.
Status: CLOSED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Java (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: Maros Sandor
URL:
Keywords: REGRESSION
Depends on:
Blocks:
 
Reported: 2004-09-18 18:33 UTC by gugrim
Modified: 2005-07-11 08:58 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
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 gugrim 2004-09-18 18:33:40 UTC 
[ BUILD # : 200409170519 ]
[ JDK VERSION : J2SE 1.4.2 ]

When running two debugging sessions, one for the
client and one attached to the server, and a
breakpoint is reached, the debugging session
withing which the breakpoint is reached is not
made current.
Comment 1 gholmer 2004-10-07 19:01:43 UTC 
I'm also seeing this with build 200409291800. Trying to debug an RMI
server and his client at the same time.
Comment 2 Jan Chalupa 2004-10-11 17:07:10 UTC 
Lubo, try to reproduce please.
Comment 3 _ lcincura 2004-10-12 09:11:02 UTC 
This is reproducible also on jdk 1.5.0 with two sessions. When
breakpoint is hit, session is not made current and no program counter
is shown. User does not know a breakpint is hit. This behaviour can be
very confusing.
Comment 4 Jan Chalupa 2004-10-12 09:29:30 UTC 
Is the problem reproducible with JDK 1.4.2? Shouldn't this be a P2?
I'd say it's a "must fix" for 4.0.
Comment 5 _ lcincura 2004-10-12 09:41:33 UTC 
It behaves same on jdk 1.4.2 and jdk 1.5.0.
It is regression from NB3.6 => P2
Comment 6 Maros Sandor 2004-10-13 14:32:10 UTC 
Updated breakpoint constructors to contain Session objects as well. 
This Session is made current after the breakpoint hits.

/cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/breakpoints/B
reakpointImpl.java,v  <--  BreakpointImpl.java
new revision: 1.12; previous revision: 1.11
/cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/breakpoints/B
reakpointsEngineListener.java,v  <--  BreakpointsEngineListener.java
new revision: 1.15; previous revision: 1.14
/cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/breakpoints/C
lassBasedBreakpoint.java,v  <--  ClassBasedBreakpoint.java
new revision: 1.8; previous revision: 1.7
/cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/breakpoints/C
lassBreakpointImpl.java,v  <--  ClassBreakpointImpl.java
new revision: 1.6; previous revision: 1.5
/cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/breakpoints/E
xceptionBreakpointImpl.java,v  <--  ExceptionBreakpointImpl.java
new revision: 1.6; previous revision: 1.5
/cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/breakpoints/F
ieldBreakpointImpl.java,v  <--  FieldBreakpointImpl.java
new revision: 1.6; previous revision: 1.5
/cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/breakpoints/L
ineBreakpointImpl.java,v  <--  LineBreakpointImpl.java
new revision: 1.16; previous revision: 1.15
/cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/breakpoints/M
ethodBreakpointImpl.java,v  <--  MethodBreakpointImpl.java
new revision: 1.6; previous revision: 1.5
/cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/breakpoints/T
hreadBreakpointImpl.java,v  <--  ThreadBreakpointImpl.java
new revision: 1.4; previous revision: 1.3
Comment 7 Max Sauer 2005-07-11 08:58:58 UTC 
I've veried it in nbdev200507061800.