From: Stan Shebs <stan@codesourcery.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: attach to a PID using a different exec
Date: Thu, 13 Nov 2008 23:24:00 -0000 [thread overview]
Message-ID: <491C895F.7030500@codesourcery.com> (raw)
In-Reply-To: <m3k5b74dnz.fsf@fleche.redhat.com>
Tom Tromey wrote:
>>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
>>>>>>
>>> This patch changes gdb to look at the target's notion of the exec
>>> file, and then switch to it if it differs from the current exec.
>>>
>
> Daniel> This seems like a bad idea to me. The canonical example is:
> Daniel> /usr/bin/prog.stripped &
> Daniel> gdb /home/drow/prog.debug $(pidof prog.stripped)
> Daniel> I don't want GDB to prompt my to switch to the stripped program...
>
> Well, you can answer "no". So while it is inconvenient, it seems
> minor. On the other hand, the current situation can leave one with a
> nonsensical setup. This bites me a lot more than I should probably
> admit.
>
For multi-exec GDB, I added a set-exec command for just this situation -
if you have multiple execs in the session, it's extremely difficult to
tell which (if any) corresponds to the attached process. In practice so
far, it's better than nothing, but we need more. We should have as many
heuristics as possible, and ask for a confirmation too. (I wonder if
comparing a handful of bytes, or sections, from each exec would be a
useful check...)
Stan
next prev parent reply other threads:[~2008-11-13 20:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 22:32 Tom Tromey
2008-11-13 22:49 ` Daniel Jacobowitz
2008-11-13 22:54 ` Tom Tromey
2008-11-13 23:24 ` Stan Shebs [this message]
2008-11-13 23:51 ` Daniel Jacobowitz
2008-11-13 22:59 ` Joel Brobecker
2008-11-13 23:17 ` Andreas Schwab
2008-11-13 23:55 ` Tom Tromey
2008-11-14 0:54 ` Michael Snyder
2008-11-14 1:53 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=491C895F.7030500@codesourcery.com \
--to=stan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox