Bugzilla – Full Text Bug Listing
| Summary: | Breakpoint appears to be stuck after a constructor has been wiped | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Remy Suen <remy.suen> | ||||
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | Michael_Rennie | ||||
| Version: | 3.8 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
*** This bug has been marked as a duplicate of bug 153925 *** |
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.