From: Daniel Jacobowitz <drow@mvista.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:06:00 -0000 [thread overview]
Message-ID: <20030617210553.GA21025@nevyn.them.org> (raw)
In-Reply-To: <200306172044.h5HKieb29320@magilla.sf.frob.com>
On Tue, Jun 17, 2003 at 01:44:40PM -0700, Roland McGrath wrote:
> > Andrew> Last I heard was a kernel patch to make auxv info available
> > Andrew> in the core file, and via the /proc and ptrace interfaces.
> >
> > Yes: auxv, core, and ptrace are there. I don't think /proc support is
> > there. Not sure if Roland is planning to do something about that.
>
> To clarify, I think what David's saying (and what I think is the case) is
> that access to these memory regions via core dumps and ptrace does work
> just like any other user address, and that the startup-time aux vector on a
> process's stack contains AT_SYSINFO_EHDR to tell the process the location.
>
> The piece that still remains missing is gdb finding out where the DSO is,
> i.e. the AT_SYSINFO_EHDR value of a traced process. For that, I've
> proposed a new /proc/PID/auxv virtual file and a new NT_AUXV note in core
> dumps (these match exactly what Solaris provides). I posted a patch to
> implement this in Linux 2.5 to lkml on May 15; it was met with resounding
> silence. Pushing that patch has not been top priority since then, since
> this issue affects gdb only with 2.5 kernels and so is not an imminent
> concern for the Red Hat products I work on.
>
> After posting that patch, I realized it had a leak. I didn't bother to
> follow up with the corrected patch immediately, since my posting of the
> first patch had failed to solicit any response of any kind even on the
> question of the interface. I would be happy to dust off that patch and
> send it to you, post it again, or send it anywhere else that would increase
> the likelihood of getting some response about it. If Linux kernel folks
> are happy enough with the interface but not with the implementation, I
> would be glad to rewrite it as requested.
Send me a copy of the update, please. I'm going to push another
debug-related patch to Linus this week anyway. He's been pretty good
about taking patches lately.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-06-17 21:06 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
2003-06-17 21:15 ` Andrew Cagney
2003-06-17 21:06 ` Daniel Jacobowitz [this message]
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=20030617210553.GA21025@nevyn.them.org \
--to=drow@mvista.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).