Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 315214 - [breakpoints] Breakpoint with old JRE path behaves strangely
Summary: [breakpoints] Breakpoint with old JRE path behaves strangely
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-01 09:47 EDT by Markus Keller CLA
Modified: 2019-03-21 20:08 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2010-06-01 09:47:26 EDT
I20100527-1700, similar in 3.5.2

- have a workspace with an outdated default JRE (mine was at C:\java\jdk6_16)
- create 3 line breakpoints in java.io.PrintStream#println(int)
- Preferences > Installed JREs
- edit the JRE and change the JRE home (to C:\java\jdk6_20 in my case)
- click "Restore Default" to make sure the system libraries are updated
- click Finish, OK

=> the breakpoints are in a strange state now:
- they look OK (no error overlay or other problem indicator)
- they still stop the target when I debug
- they are not visible in the editor ruler any more
- they don't react on double-click in the Breakpoints view
- the details pane in the Breakpoints view shows wrong state (e.g. when I select a breakpoint with a condition and then select a broken breakpoint, the "Conditional" checkbox stays checked, but the condition is empty and cannot be saved).

The Breakpoint Properties dialog shows an error message "C:\java\jdk6_16\jre\lib\rt.jar is not on its project's build path".
Comment 1 Eclipse Genie CLA 2019-03-21 20:08:19 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.