Bug 559752 - breakpoints get incorrectly moved after some edits
Summary: breakpoints get incorrectly moved after some edits
Status: CLOSED DUPLICATE of bug 546957
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.14   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL: https://www.dropbox.com/s/o0xgcsa2cej...
Whiteboard:
Keywords: bugday, test, ui, usability
Depends on:
Blocks:
 
Reported: 2020-01-31 10:31 EST by james tomkinson CLA
Modified: 2020-05-17 17:26 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description james tomkinson CLA 2020-01-31 10:31:49 EST
I often find my breakpoint moved one or more lines after editing, perhaps after a paste operation.   this is especially impacting if:
- from a if-then-else "then" clause to the "if" clause
- from try-catch "catch" clause back into the "try" clause.
if the clause contains older, complex break condition code, it is especially difficult to correct.

Ignoring the obvious comment that this shouldn't happen,

If would be nice to have a feature where I could either:
- drag a breakpoint to a new line
- cut/paste a breakpoint to a different line
- edit the breakpoint to change the line


image: https://www.dropbox.com/s/o0xgcsa2cej1rwk/breakpoint_moved.PNG

-- Configuration Details --
Product: Eclipse IDE 4.14.0.20191212-1200 (org.eclipse.epp.package.jee.product)Installed Features:
 org.eclipse.jdt 3.18.200.v20191210-0610
Versioning Plugin:
 org.eclipse.platform 4.14.0.v20191210-0610
Comment 1 Sarika Sinha CLA 2020-02-02 23:25:34 EST
Can you please provide exact snippet to reproduce because if edits lead to a non executable statement, a breakpoint can jump to next valid statement.
Comment 2 james tomkinson CLA 2020-05-17 17:26:27 EDT
this should probably be merged or a dup of
https://bugs.eclipse.org/bugs/show_bug.cgi?id=546957
Comment 3 james tomkinson CLA 2020-05-17 17:26:46 EDT

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