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 7122 - CTRL+F8 breakpoint on a line of a running debugged session is not always valid where it should be valid
Summary: CTRL+F8 breakpoint on a line of a running debugged session is not always vali...
Status: CLOSED WONTFIX
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: All All
: P4 major (vote)
Assignee: Jan Jancura
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-07-20 11:27 UTC by Antonin Nebuzelsky
Modified: 2003-06-30 17:27 UTC (History)
0 users

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 Antonin Nebuzelsky 2000-07-20 11:27:32 UTC 
[2010]
Win2000 (jdk1.2.2, jdk1.3), Solaris 8 (jdk1.2.2)
JDK1.1 debugger, JPDA debugger

Assumptions:
- A session running in debug mode
- Debugging workspace with debugger window displayed
- The session being debugged opened in Editor window

Action:
- Press CTRL+F8 on a line of the session in Editor window
where the breakpoint must be valid

Results:
- the line is highlighted
- the breakpoint appears in Breakpoints tab of Debugger window
- BUT the property Valid is set to False !!!
-> the application does not stop on this breakpoint

Notes:
- On some lines the breakpoint is set valid but on some lines it is not
- When you stop the debugger and start it again, the nonvalid breakpoint
BECOMES VALID !!!
Comment 1 Antonin Nebuzelsky 2000-07-20 11:33:59 UTC 
Tested on:
- Memory View, lines 88-109 (method updateStatus)
Comment 2 Antonin Nebuzelsky 2000-07-20 16:01:59 UTC 
This bug was not in fact bug of the debugger. It was caused by inconsistency of
java and class files of the IDE java examples that I used to test the debugger.
The examples were recompiled and checked back into CVS so in the next build
([2011]) everything should be OK.
Comment 3 Antonin Nebuzelsky 2000-07-26 12:37:59 UTC 
This bug still exists in one special case:
Solaris + jdk1.2.2_05a + JPDA debugger
In this case ALL line breakpoints added to a running debugged session are
invalid. They become valid only after restarting the debugger.
Comment 4 Daniel Prusa 2000-07-27 09:06:59 UTC 
There is a bug in JDK1.2.2_05a. Information needed to set a breakpoint cannot be
obtained in the described case. (com.sun.jdi.ReferenceType.locationsOfLine (int)
throws com.sun.jdi.AbsentInformationException)
Comment 5 Jan Stola 2000-07-27 17:37:59 UTC 
Bug assigned to the module owner.
Comment 6 Quality Engineering 2003-06-30 17:27:35 UTC 
Resolved for 3.3.x or earlier, no new info since then -> closing.