This is the mail archive of the
mailing list for the GDB project.
Re: [PATCH 6/6] Implement proper "startup-with-shell" support on gdbserver
- From: Sergio Durigan Junior <sergiodj at redhat dot com>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: gdb-patches at sourceware dot org, palves at redhat dot com
- Date: Thu, 05 Jan 2017 15:12:02 -0500
- Subject: Re: [PATCH 6/6] Implement proper "startup-with-shell" support on gdbserver
- Authentication-results: sourceware.org; auth=none
- References: <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com>
On Wednesday, January 04 2017, Eli Zaretskii wrote:
>> From: Sergio Durigan Junior <firstname.lastname@example.org>
>> Cc: email@example.com, firstname.lastname@example.org
>> Date: Tue, 03 Jan 2017 15:48:26 -0500
>> > Also, is it possible that a user will want
>> > remote targets to use a shell, while avoiding that for native
>> > debugging, in the same session?
>> Yeah, I thought about that. My first thought was to add a 'set/show
>> remote startup-with-shell' option, but I thought this was going to be
>> too much for the user. Maybe not.
>> With this new setting, we'd have:
>> - startup-with-shell: Used only locally, default on. Instructs GDB to
>> start the inferior using the shell.
>> - remote startup-with-shell: Used only remotely, default on. Instructs
>> gdbserver to start the inferior using the shell.
>> - remote startup-shell: Used only remotely (if remote startup-with-shell
>> is on), default "" (empty). Tells which shell to be used by gdbserver
>> to start the inferior. If empty, use $SHELL.
> Makes sense to me, thanks.
Cool, thanks. I'll go ahead and implement this idea, then.
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible