From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [wip] "info auxv"
Date: Mon, 10 Nov 2003 23:21:00 -0000 [thread overview]
Message-ID: <20031110232139.GA20227@nevyn.them.org> (raw)
In-Reply-To: <3FB01C47.1020502@redhat.com>
On Mon, Nov 10, 2003 at 06:16:23PM -0500, Andrew Cagney wrote:
> This work-in-progress is more questions than answers.
>
> - Common code in "procfs.c" (tested) and "inftarg.c"
> It makes me wonder if the native inferior code should be re-arranged
> (has this come up before?).
>
> - The new files "auxv.[hc]" for parsing the file.
> Perhaphs it belongs in "procfs.c" but that gets me back to the first
> question - could the native inferior code be better structured?
> + switch (auxv.type)
> + {
> + case AT_NULL:
> + name = "End of vector";
> + break;
Just a comment - as Roland said, the values in "elf/common.h" are not
authoritive, and I don't even think they match Solaris? Should this be
in common code?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-11-10 23:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 23:16 Andrew Cagney
2003-11-10 23:21 ` Daniel Jacobowitz [this message]
2003-11-11 15:48 ` Andrew Cagney
2003-11-11 15:57 ` Daniel Jacobowitz
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=20031110232139.GA20227@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.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