Community
Participate
Working Groups
It would be helpful for me to be able to move a breakpoint. I work with many conditional breakpoints that I often want to move. Currently that means opening the breakpoint properties dialog, copy the conditional, make a new breakpoint, open the breakpoint properties dialog, paste the conditional. Possible implementations of this (would be nice to have all of them): 1. Drag and drop of the breakpoint in the editor. 2. Editable line number in breakpoint properties page. 3. Copy/paste feature for breakpoints, i.e. select breakpoint, copy, paste, dialog prompts for new location.
1 & 2. dup of bug 15001 3. New feature request Marking 15001 as a dup of this bug.
*** Bug 15001 has been marked as a duplicate of this bug. ***
Marking as later
*** Bug 25192 has been marked as a duplicate of this bug. ***
*** Bug 71897 has been marked as a duplicate of this bug. ***
*** Bug 98288 has been marked as a duplicate of this bug. ***
is this going to happen? it's very frustrating when I specify a complex condiion in the breakpoint that I cannot move it (or save it - but that's another bug) the line number property should be editable from the 'breakpoint properties' dialog.
*** Bug 20597 has been marked as a duplicate of this bug. ***
*** Bug 163819 has been marked as a duplicate of this bug. ***
*** Bug 165486 has been marked as a duplicate of this bug. ***
reopening
*** Bug 193755 has been marked as a duplicate of this bug. ***
*** Bug 199604 has been marked as a duplicate of this bug. ***
*** Bug 211758 has been marked as a duplicate of this bug. ***
*** Bug 281048 has been marked as a duplicate of this bug. ***
*** Bug 321034 has been marked as a duplicate of this bug. ***
There's an additional reason to want this kind of functionality. I use the JD-Eclipse plugin for decompiling bytecode. With this, I can step through decompiled code, although somewhat awkwardly. The decompiled code gets margin comments with the original line numbers, which won't correspond to the line numbers in the resulting decompiled source. I quite often have to scroll through the file each time I step over a line, as it tries to make itself view the current line number, which is in a different place in the file. What's even more awkward is trying to set breakpoints in the decompiled source. For instance, if I want to set a breakpoint on (original)line 212 in a class, I have to scroll down to line 212 in the decompiled source and hope for two things: * The file is actually that long. If the file is shorter than that, I can't set the breakpoint. * There is a breakpoint-able line of code on that line in the decompiled source. If it's not valid for breakpoints, I can't set the breakpoint. If I could set breakpoints on a line number entered by me, or change the line number on an entered breakpoint, then I could get around this problem.
*** Bug 336627 has been marked as a duplicate of this bug. ***
I don't think we have generic APIs to implement this kind of feature, it'd have to be done by individual debuggers.
(In reply to comment #19) > I don't think we have generic APIs to implement this kind of feature, it'd have > to be done by individual debuggers. We do now have bp condition histories, which would mitigate problem of losing complex conditions in the event the bp had to be removed / replaced.
(In reply to comment #20) The bp condition history only helps if the condition was recently changed. But if you want to enable an older breakpoint and the underlying source has been changed since you created it, you still have to copy/paste the condition. An editable line number in the Properties dialog would be easy to do. DND of breakpoints in the editor ruler would need more support from the editor, see AbstractTextEditor#getRulerMouseListener(). (In reply to comment #19) > I don't think we have generic APIs to implement this kind of feature, it'd have > to be done by individual debuggers. I think the most common use case is to move an ILineBreakpoint by a few lines while retaining all other properties of the bp. I think this would be interesting in all kinds of languages, not only in Java.
> (In reply to comment #19) > > I don't think we have generic APIs to implement this kind of feature, it'd have > > to be done by individual debuggers. > > I think the most common use case is to move an ILineBreakpoint by a few lines > while retaining all other properties of the bp. I think this would be > interesting in all kinds of languages, not only in Java. I don't disagree, it's just how our debugger APIs are structured. Except for the generic toggle breakpoint actions (ctrl-shift-B), the individual debugger implementations are responsible for supplying all other breakpoint creation and editing actions. For example in Wind River's debugger we do allow users to change the BP line number in the breakpoint properties view. I don't know if users really care about it though. DND would be much more useful.
what about this feature request. Will be implemented?
(In reply to comment #23) > what about this feature request. Will be implemented? Not at this point.
Could be in the next big release, Kepler? It is a requests since 2002... It would help many developers
(In reply to comment #25) > Could be in the next big release, Kepler? It is a requests since 2002... It > would help many developers Only if someone provides a high quality patch.
I do wonder, is this considered and will it ever be added? Wanted to move a breakpoint, was hopeful when I saw the input field in the ide. But it was locked. Does seem people are still searching for it and could use it https://stackoverflow.com/questions/14850620/how-can-i-move-a-conditional-breakpoint-in-eclipse
