Bug 153925 - [breakpoints] Line breakpoint is outside of method body
Summary: [breakpoints] Line breakpoint is outside of method body
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
: 167764 258089 273242 365430 366209 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-08-15 11:35 EDT by Benno Baumgartner CLA
Modified: 2022-06-12 12:45 EDT (History)
6 users (show)

See Also:

Attachments
screenshot (127.63 KB, image/png)
2006-08-15 11:36 EDT, Benno Baumgartner 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 Benno Baumgartner CLA 2006-08-15 11:35:31 EDT 
I20060810-1230

I'm not sure how, but I did end up with a line breakpoint outside of a method. I can't toggle this breakpoint anymore. See screenshot...

The breakpoint was set on line 174 then I did some copy/cut/paste commend/uncommend code and then I saw that the line breakpoint did end up in the middle of nowhere.

Remove all breakpoints does work.
Nothing in the log.
Comment 1 Benno Baumgartner CLA 2006-08-15 11:36:01 EDT 
Created attachment 47924 [details]
screenshot
Comment 2 Michael Rennie CLA 2006-08-22 17:45:27 EDT 
We have seen this happen before, this can occur because the marker for the breakpoint is no updated properly as you cut/copy/paste, etc.

I have added a breakpoint marker updater, that will update the position of the breakpoint marker more effectively.

See BreakpointMarkerUpdater in jdt.debug.ui for fix and its corresponding javadoc for the cases it prevents when updating breakpoint markers.
Comment 3 Michael Rennie CLA 2006-08-22 17:46:34 EDT 
please verify Kevin
Comment 4 Michael Rennie CLA 2006-12-12 15:02:57 EST 
reopen to reasign
Comment 5 Michael Rennie CLA 2006-12-12 15:03:58 EST 
please verify Darin W
Comment 6 Darin Wright CLA 2006-12-14 11:06:47 EST 
This can still happen by following the steps in bug 167764:

* In a class in the *default* package, put a breakpoint on the first line of a method.
* Move the class to a non-default package

> line breakpoint is on the method decl line and cannot be removed by double-click in ruler.
Comment 7 Darin Wright CLA 2006-12-14 11:07:26 EST 
*** Bug 167764 has been marked as a duplicate of this bug. ***
Comment 8 Darin Wright CLA 2007-05-17 14:28:21 EDT 
Not planned for 3.3
Comment 9 Darin Wright CLA 2008-12-09 09:58:15 EST 
*** Bug 258089 has been marked as a duplicate of this bug. ***
Comment 10 Michael Rennie CLA 2010-12-07 13:05:25 EST 
3.7M4, this can still happen by following the steps in bug 167764
Comment 11 Michael Rennie CLA 2011-03-23 14:48:48 EDT 
*** Bug 273242 has been marked as a duplicate of this bug. ***
Comment 12 Michael Rennie CLA 2011-12-12 10:04:09 EST 
*** Bug 366209 has been marked as a duplicate of this bug. ***
Comment 13 Michael Rennie CLA 2012-03-15 16:40:28 EDT 
*** Bug 365430 has been marked as a duplicate of this bug. ***
Comment 14 Eclipse Genie CLA 2020-06-21 20:21: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.
Comment 15 Eclipse Genie CLA 2022-06-12 12:45: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.

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.