Version: 4.2.1 (using KDE 4.6.0) OS: Linux This is more in the category "nuisance": When debugging an executable, there are occasions where you want to enter a gdb command, e.g. to call a function in the program and see its output. The GDB interface offers this ability through the text field "GDB command" in the "GDB" tool. However, when I enter a command into this field, I get the following error every time: Gdb command sent when debugger is not running The command was: <the command I entered> The error message is spurious: gdb is in fact running, and the command is also executed, with the result anticipated. I don't know what causes the error code. Best & thanks Wolfgang Reproducible: Didn't try Steps to Reproduce: Start an executable in the debugger, set a breakpoint, when there enter any commend -- "backtrace" for example will suffice and should work on any program at any location. Actual Results: Error message + correct output Expected Results: Correct output.
I noticed this behavior as well. However, sometimes the entered command is executed directly, sometimes the described error message is shown once, and sometimes even several times before the execution. I could not figure out yet, on which circumstances this differences depend, though when entering a sequence of commands the number of shown error messages remains the same for each command. My kdevelop version is 4.2.2 (KDE platform 4.6.5)
Still occurs with kdevelop version 4.2.3 (KDE platform 4.8 RC2 (4.7.97) )
I can't reproduce this issue, for me executing a custom command works without this error message. Please help me on this: - try to reproduce with current git version form 4.3 branch (or master) - post debug output (enable gdb plugin in "kdebugdialog")
please provide more information on this issue.
Created attachment 69639 [details] Output of kdevelop when problem occured Here is the debugging output you asked for. It is a quite a lot, so it should be best to start reading from the back of the file. The gdb command "catch throw" yielded the "Gdb command send when debugger is not running" dialog. I interrupted the output after clicking on "ok". The output does not start with the start of kdevelop but contains just the first debugging run where the problem occured, since there is a limit on the size of files I can upload here.
output supplied, changing status
I can't reproduce this issue and the debug output you provided unfortunately doesn't help. Please try with 4.3.0 (or the 4.3 branch) if you can reproduce and post the output again.
still can't reproduce, please reopen if someone has more info.
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!
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!