Bug 408342

Summary:	Remote debugging gdbserver is not closed
Product:	[Applications] kdevelop	Reporter:	Martin <martin.marmsoler>
Component:	Embedded systems support	Assignee:	kdevelop-bugs-null
Status:	REPORTED ---
Severity:	normal	CC:	mail, patrickelectric
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Martin 2019-06-05 12:38:57 UTC

I'm using gdb in KDevelop to remote debug, for this I have a shell script, which copies the executable to the target(raspberry pi) and starts there a gdbserver with the executable. After that gdb calls a script to connect to the remote server.

"file Multikopter
target remote 192.168.0.101:12345
b main
continue"

First: Why do I have to do "file Multikopter" to add the executable to the gdb? Otherwise the executable is not found and the debugging does not work.

When I'm connected and after debugging click the stop button, the client is closed, but the gdb server is running. So a second time to connect is anymore possible. Is there a possibility to stop the gdbserver too?
When the program stopped at a breakpoint it stops fine and closes the gdbserver.

STEPS TO REPRODUCE
1. start gdbserver with executable on target
2. connect to gdbserver from host
3. stop

OBSERVED RESULT
The program is running, but the debugger is anymore running

EXPECTED RESULT
The program stops too.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION