This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 1/8] Disallow using --attach and --wrapper together.
- From: Pedro Alves <palves at redhat dot com>
- To: Yao Qi <qiyaoltc at gmail dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 24 Jul 2015 09:51:17 +0100
- Subject: Re: [PATCH 1/8] Disallow using --attach and --wrapper together.
- Authentication-results: sourceware.org; auth=none
- References: <1437392126-29503-1-git-send-email-yao dot qi at linaro dot org> <1437392126-29503-2-git-send-email-yao dot qi at linaro dot org> <55B16AC0 dot 4090808 at redhat dot com> <86k2tqgd2c dot fsf at gmail dot com>
On 07/24/2015 09:44 AM, Yao Qi wrote:
> Pedro Alves <palves@redhat.com> writes:
>
>> Really not sure about this. It's reasonable to do e.g.,
>> alias gs="gdbserver --wrapper=/whatever/wrapper --"
>> (or the equivalent wrapper shell script that execs gdbserver)
>> and then always start that instead of gdbserver:
>>
>> sometimes:
>>
>> $ gs :9999 PROGRAM
>>
>> othertimes:
>>
>> $ gs --attach :9999 $pid
>>
>> but after the patch, the latter errors out.
>
> IMO, it makes sense to error out in the latter case, because --wrapper
> is useless if GDBserver attaches to a process.
The point was that before you could just forget about --wrapper,
set it once for your target/environment, having it hidden in the
script|alias-that-wraps-gdbserver. I see it the same as putting
this in ~/.gdbinit:
set exec-wrapper /whatever/wrapper
and then doing "$ gdb -p PID", and having GDB complain
about "set exec-wrapper" and "-p" being incompatible.
>
>>
>> Plus, one can combine --attach and --multi, which means
>> that the wrapper would still apply to processes spawned
>> after connecting.
>
> I agree on this case. I withdraw this patch.
>
Thanks,
Pedro Alves