Bug 378237 - KDevelop doesn't move the screen with the line indicator when stepping through the code in Debug
Summary: KDevelop doesn't move the screen with the line indicator when stepping throug...
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: CPP Debugger (show other bugs)
Version: git master
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-29 11:59 UTC by Petros
Modified: 2022-12-10 05:14 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Petros 2017-03-29 11:59:24 UTC
When I step through the code in Debug mode, the line indicator (which looks like an arrow an point at the next statement) sometimes jumps to another part of the source code/another function and goes out of sight.

So I have to scroll here and there to actually see where the execution flow goes. Maybe the line indicator should have some kind of limit, or a margin of the screen that is allowed to exist. Eg if the indicator moves X numbers before the visible code's end, then the editor should auto scroll the code in order the indicator to be at Y lines above the middle of the shown code.
Comment 1 Petros 2017-03-29 12:01:15 UTC
Also, if the indicator goes suddenly out of sight because let's say it jumped in a different function, KDevelop also could autoscroll there
Comment 2 Jeremy W. Murphy 2018-01-04 23:23:57 UTC
I have also seen this happen several times in the past, but I'm not sure how to reproduce it reliably.
Come to think of it, I haven't seen it happen recently; have you?
Comment 3 Petros 2018-01-09 13:34:34 UTC
I can't reproduce it either. It's been a long time since I last tried to debug a project in KDevelop.

Maybe they fixed it.
Comment 4 Justin Zobel 2022-11-10 22:33:15 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2022-11-25 05:16:47 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2022-12-10 05:14:01 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!