Bug 271145

Summary:	Debugger "GDB command" always reports error
Product:	[Applications] kdevelop	Reporter:	Wolfgang Bangerth <bangerth>
Component:	CPP Debugger	Assignee:	kdevelop-bugs-null
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	aleixpol, markus.parker, niko.sams
Priority:	NOR	Keywords:	triaged
Version First Reported In:	4.2.1
Target Milestone:	4.2.0
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Output of kdevelop when problem occured

Description Wolfgang Bangerth 2011-04-17 06:01:29 UTC

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.

Comment 1 markus.parker 2011-07-15 11:50:52 UTC

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)

Comment 2 Stephan Burkhardt 2012-01-19 16:32:50 UTC

Still occurs with kdevelop version 4.2.3 (KDE platform 4.8 RC2 (4.7.97) )

Comment 3 Niko Sams 2012-01-22 13:57:24 UTC

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")

Comment 4 Niko Sams 2012-03-11 17:31:03 UTC

please provide more information on this issue.

Comment 5 markus.parker 2012-03-15 12:09:09 UTC

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.

Comment 6 Milian Wolff 2012-03-22 09:28:39 UTC

output supplied, changing status

Comment 7 Niko Sams 2012-03-24 08:58:26 UTC

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.

Comment 8 Niko Sams 2012-10-24 22:36:28 UTC

still can't reproduce, please reopen if someone has more info.

Comment 9 Andrew Crouthamel 2018-09-23 02:43:34 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 10 Andrew Crouthamel 2018-10-27 02:04:58 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!