From: David Mosberger <davidm@napali.hpl.hp.com>
To: Roland McGrath <roland@redhat.com>
Cc: davidm@hpl.hp.com, gdb@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: [davidm@napali.hpl.hp.com: readelf question]
Date: Tue, 17 Jun 2003 21:00:00 -0000 [thread overview]
Message-ID: <16111.33109.103581.40103@napali.hpl.hp.com> (raw)
In-Reply-To: <200306172044.h5HKieb29320@magilla.sf.frob.com>
>>>>> On Tue, 17 Jun 2003 13:44:40 -0700, Roland McGrath <roland@redhat.com> said:
Roland> The piece that still remains missing is gdb finding out
Roland> where the DSO is, i.e. the AT_SYSINFO_EHDR value of a traced
Roland> process. For that, I've proposed a new /proc/PID/auxv
Roland> virtual file and a new NT_AUXV note in core dumps (these
Roland> match exactly what Solaris provides).
Sounds reasonable to me. Is /proc/PID/auxv really needed, though?
Isn't it easy enough to get to the aux vector from the initial stack
pointer (which gdb could catch from /proc/PID/stat).
Roland> I posted a patch to implement this in Linux 2.5 to lkml on
Roland> May 15; it was met with resounding silence.
That may not mean much. Clearly it makes no sense to implement half a
solution to the problem and given that the first half is in, I don't
expect any issues in getting the rest (or some alternative) in.
Andrew Morton is very good at collecting misc. patches, providing
feedback, and feeding them on to Linus, so you might want to talk to
him (please do cc me, too; I don't have much time to work on this
myself, but I do want to make sure the ia64 portion stays in sync).
--david
next prev parent reply other threads:[~2003-06-17 21:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 14:57 H. J. Lu
2003-06-17 8:14 ` Nick Clifton
2003-06-17 18:56 ` David Mosberger
2003-06-17 19:27 ` Andrew Cagney
2003-06-17 20:14 ` David Mosberger
2003-06-17 20:41 ` Andrew Cagney
2003-06-17 20:44 ` Roland McGrath
2003-06-17 21:00 ` David Mosberger [this message]
2003-06-17 21:15 ` Andrew Cagney
2003-06-17 21:06 ` Daniel Jacobowitz
2003-06-17 20:26 ` Roland McGrath
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=16111.33109.103581.40103@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=binutils@sources.redhat.com \
--cc=davidm@hpl.hp.com \
--cc=gdb@sources.redhat.com \
--cc=roland@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