From: Mark Kettenis <kettenis@science.uva.nl>
To: drow@mvista.com
Cc: msnyder@cygnus.com, gdb-patches@sources.redhat.com, kevinb@redhat.com
Subject: Re: [RFA] Find and read symbol files after attach (linux)
Date: Tue, 08 Jan 2002 10:12:00 -0000 [thread overview]
Message-ID: <200201081810.g08IADo26690@debye.wins.uva.nl> (raw)
In-Reply-To: <20020107215957.A9170@nevyn.them.org> (message from Daniel Jacobowitz on Mon, 7 Jan 2002 21:59:57 -0500)
Date: Mon, 7 Jan 2002 21:59:57 -0500
From: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com, kettenis@science.uva.nl, kevinb@redhat.com
Mail-Followup-To: Michael Snyder <msnyder@cygnus.com>,
gdb-patches@sources.redhat.com, kettenis@science.uva.nl,
kevinb@redhat.com
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.23i
X-Status:
X-Keywords:
X-UID: 16
On Mon, Jan 07, 2002 at 04:40:00PM -0800, Michael Snyder wrote:
> [oops, hit send too soon...]
> This change allows GDB to find and read the symbol files (including
> all shared libraries) on Linux when you attach to an anonymous PID.
> It should work for all Linuxen, but for now I've only added it to the
> linux.mh and nm-linux.h files in config/i386. Please feel free to
> add it to your targets.
[without actually looking at it...]
[...for both of us]
(B) Why do we need /proc to do this? We should be able to use the
information in the link map - which we already access in solib-svr4.h -
to get all of this.
Nope. You can't get at the executable itself this way.
Mark
next prev parent reply other threads:[~2002-01-08 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-07 18:20 Michael Snyder
2002-01-07 19:00 ` Daniel Jacobowitz
2002-01-08 10:12 ` Mark Kettenis [this message]
[not found] ` <3C3B332E.774C4E2E@redhat.com>
2002-01-08 10:36 ` Daniel Jacobowitz
2002-01-08 15:15 ` Michael Snyder
-- strict thread matches above, loose matches on Subject: below --
2002-01-07 18:20 Michael Snyder
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=200201081810.g08IADo26690@debye.wins.uva.nl \
--to=kettenis@science.uva.nl \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@redhat.com \
--cc=msnyder@cygnus.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