Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 365430 - Breakpoint appears to be stuck after a constructor has been wiped
Summary: Breakpoint appears to be stuck after a constructor has been wiped
Status: CLOSED DUPLICATE of bug 153925
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.8   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-02 08:52 EST by Remy Suen CLA
Modified: 2012-03-15 16:40 EDT (History)
1 user (show)

See Also:

Attachments
Screenshot depicting the state in question. (49.75 KB, image/png)
2011-12-02 08:52 EST, Remy Suen 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 Remy Suen CLA 2011-12-02 08:52:39 EST 
Created attachment 207841 [details]
Screenshot depicting the state in question.

I added a constructor in ModelServiceImpl and then I did a hard reset to get my branch's content clean. The original version of the file does not have the constructor. Somehow it still thinks I have a breakpoint in that constructor and trying to unset it back at line 61 does remove the breakpoint. I imagine that wouldn't have worked if I didn't have code at line 61.

Note though that the phantom breakpoint was rendered in line 58 and not at line 61.
Comment 1 Michael Rennie CLA 2012-03-15 16:40:28 EDT 

*** This bug has been marked as a duplicate of bug 153925 ***