This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Make only user-specified executable filenames sticky
- From: Doug Evans <dje at google dot com>
- To: Pedro Alves <palves at redhat dot com>
- Cc: Gary Benson <gbenson at redhat dot com>, gdb-patches <gdb-patches at sourceware dot org>, Philippe Waroquiers <philippe dot waroquiers at skynet dot be>
- Date: Tue, 12 May 2015 09:03:34 -0700
- Subject: Re: [PATCH] Make only user-specified executable filenames sticky
- Authentication-results: sourceware.org; auth=none
- References: <20150505151448 dot GA1417 at blade dot nx> <1430907977-30605-1-git-send-email-gbenson at redhat dot com> <CADPb22SDB9qV1BgP2JmCxsu-E8QXDj1SLnCjBjGWn+g+1M7V7A at mail dot gmail dot com> <5551D7AD dot 8080500 at redhat dot com>
On Tue, May 12, 2015 at 3:36 AM, Pedro Alves <palves@redhat.com> wrote:
> Another way to handle that would be to leave the file loaded
> in inferior 1, and switch to a new inferior to investigate
> the other process.
Sorry, these things don't always occur to me before I hit Send.
Switching to a new inferior is three steps.
(gdb) add-inf
(gdb) infer 2
(gdb) attach PID
IWBN to have something like the following
(gdb) attach -n PID # "n" for "in new inferior"
I kinda would rather do it differently, because it's more than
just "attach" where one would like to do something in a new inferior,
and IWBN to solve them all with one new command (or extension
of existing command). E.g., "new-inferior <command>", as in
"new-inferior attach PID". Or some such.
OTOH, "new-inferior pwd" doesn't make much sense,
and "attach -n PID" is simple (we'd want to enumerate
all such commands and make sure the same option letter is
available for use in all of them).