Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 369164 - [breakpoints] Breakpoint annotation on wrong line after double rename.
Summary: [breakpoints] Breakpoint annotation on wrong line after double rename.
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.8   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-19 20:07 EST by Pawel Piech CLA
Modified: 2020-05-20 11:59 EDT (History)
0 users

See Also:

Attachments
Screenshot of misaligned breakpoint. (144.56 KB, image/png)
2012-01-19 20:07 EST, Pawel Piech CLA 		no flags Details
View All 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 Pawel Piech CLA 2012-01-19 20:07:03 EST 
Created attachment 209782 [details]
Screenshot of misaligned breakpoint.

Version: 3.7.1
Build id: M20120118-0800

I was following the test script for Refactoring: http://wiki.eclipse.org/Debug/Test_Script#Refactoring, while using the ManyVariableTypes example.  I had 2 breakpoints set and renamed it once, then renamed it again back to original name.  After the second rename, the breakpoint annotations in the gutter were shifted one line up.  (see screenshot).

I was able to reproduce the bug intermittently.
Comment 1 Eclipse Genie CLA 2020-05-20 11:59:58 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.