Bug 268239 - [breakpoints][refactor] Renaming method resulted in two method breakpoints at the same location
Summary: [breakpoints][refactor] Renaming method resulted in two method breakpoints at...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-11 18:54 EDT by Samantha Chan CLA
Modified: 2022-08-20 17:21 EDT (History)
0 users

See Also:

Attachments
screen cap (51.06 KB, image/jpeg)
2009-03-11 18:55 EDT, Samantha Chan 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 Samantha Chan CLA 2009-03-11 18:54:48 EDT 
Testcase:  BreakpointTests

1.  Add method breakpoint at BreakpointTests constructor
2.  Add method breakpoint to the foo method right under this contructor
3.  Select foo method and rename to foo2

Look at the breakpoints view.  The method at BreakpointTests constructor is now gone.  You will see too method breakpoints at foo2().
Comment 1 Samantha Chan CLA 2009-03-11 18:55:58 EDT 
Created attachment 128474 [details]
screen cap
Comment 2 Samantha Chan CLA 2009-03-11 19:06:21 EDT 
Similar problem with watchpoint.

Renaming a field could cause "adjacent" watchpoints to be overwritten.
Comment 3 Eclipse Genie CLA 2020-07-21 15:23:50 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.
Comment 4 Eclipse Genie CLA 2022-08-20 17:21:46 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.