Bug 235501 - Typing gdb commands causes an error message "Gdb command sent when debugger is not running"
Summary: Typing gdb commands causes an error message "Gdb command sent when debugger i...
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: CPP Debugger (other bugs)
Version First Reported In: 3.10.2
Platform: Compiled Sources Unspecified
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2010-04-27 00:51 UTC by Dima Ryazanov
Modified: 2018-10-27 04:17 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dima Ryazanov 2010-04-27 00:51:48 UTC
Version:           3.10.2 (using KDE 4.4.2)
Installed from:    Compiled From Sources

I tried using the GDB command line while debugging my program. It used to work earlier; however, now, each time I enter a command, I get a dialog box with the title "Internal error - KDevelop" and message:

"Gdb command sent when debugger is not running
The command was:
[the command I typed]"

After I click "Ok", GDB successfully executes the command - but the dialog box is very annoying.
Comment 1 Niko Sams 2010-04-27 09:05:38 UTC
can you reproduce the issue?
If so, please provide the needed steps.
Comment 2 Milian Wolff 2010-09-27 14:23:15 UTC
still waiting for info on how to reproduce
Comment 3 Mark Shannon 2015-05-03 21:41:35 UTC
I am seeing this bug as well.

I am trying to debug a modified version of CPython, which terminates with an assertion failure.
If I then pass a print command to gdb "p f" I see the above error.
I am using Version 4.6.0 running on kubuntu.
Comment 4 Andrew Crouthamel 2018-09-25 21:41:12 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 set the bug status 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 5 Andrew Crouthamel 2018-10-27 04:17:29 UTC
Dear Bug Submitter,

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!