Bug 559721 - The debugger moves the cursor on a code change to the active method
Summary: The debugger moves the cursor on a code change to the active method
Status: REOPENED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.13   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2020-01-30 12:42 EST by William R. Burdick Jr. CLA
Modified: 2024-01-24 06:38 EST (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 William R. Burdick Jr. CLA 2020-01-30 12:42:03 EST
When the debugger is active and I save a code change to the current method, it moves the editing cursor to the top of the method.
Comment 1 Sarika Sinha CLA 2020-01-31 01:26:59 EST
Yes, this is by design. After hot code replacements, the method is run from starting.

Please reopen and provide the details if I did not understand the problem.
Comment 2 William R. Burdick Jr. CLA 2020-02-11 17:55:16 EST
I'm talking about the edit cursor, not the indicator of which line is executing. 

I save a method, hit return and type something and, "whoops!" the code is magically inserted at the top of the method.

It's fine if the little arrow in the left-side trough moves but it is not fine if it yanks my editing cursor someplace else.
Comment 3 Sarika Sinha CLA 2020-02-12 05:20:21 EST
Ok, yes. Perhaps the "Drop to frame" can be smart enough to do that.
Comment 4 Eclipse Genie CLA 2022-02-02 15:01:05 EST
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 5 Eclipse Genie CLA 2024-01-24 06:38:05 EST
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.