Bug 507403 - Keeping GDB alive after last process exists in a remote session can lead to confusion
Summary: Keeping GDB alive after last process exists in a remote session can lead to c...
Status: ASSIGNED
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug-dsf-gdb (show other bugs)
Version: 9.0.0   Edit
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-11 09:03 EST by Marc Khouzam CLA
Modified: 2020-09-04 15:19 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Khouzam CLA 2016-11-11 09:03:32 EST 
Our remote debugging session (automatic or manual) currently uses GDB's 'remote' protocol (versus the 'extened-remote' protocol, which we use for remote attaching).

With the 'remote' protocol, gdbserver will terminate once the inferior terminates.

In this case, if we use the preference to keep GDB alive once the last inferior has terminated, GDB will remain, but gdbserver won't.  This means that if the user restarts the inferior, it will be started locally instead of remotely!
Comment 1 Marc Khouzam CLA 2016-11-13 20:18:07 EST 
I think what we could do is kill GDB when the remote shell exists.