From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] auxv support
Date: Fri, 30 Jan 2004 19:03:00 -0000 [thread overview]
Message-ID: <20040130190357.GA18536@nevyn.them.org> (raw)
In-Reply-To: <200401290259.i0T2x1c6001143@magilla.sf.frob.com>
On Wed, Jan 28, 2004 at 06:59:01PM -0800, Roland McGrath wrote:
> Ok, I think this is looking pretty polished now. I've tested it on Linux
> and Solaris. On both systems I tested the live process case, the core file
> case, and gcore. I did not test a multithreaded Solaris program, so that
> trivial part of the code path has not actually been exercised.
>
> This adds the underlying support we talked about before, implemented
> basically the same as my earlier patch. It also adds the `info auxv'
> command as Andrew proposed, but with slightly nicer output. The function
> for reading /proc/PID/auxv, and some of the other code previously
> duplicated between the procfs and linux implementations, is now shared code
> in auxv.c. There is also a utility function there that is what's needed
> for finding a single known tag's value, as some hook will do to check for
> AT_SYSINFO_EHDR.
I've reviewed this patch. I think that it's OK, although I have one
comment:
> +int
> +target_auxv_parse (struct target_ops *ops, char **readptr, char *endptr,
> + CORE_ADDR *typep, CORE_ADDR *valp)
I don't see any point in having OPS here, and it's neither used nor
described in the comment.
Since Andrew submitted a previous patch for the same feature, I'd
appreciate it if he would look over this also.
> I would like to add remote protocol and gdbserver support as well, but
> someone knowledgeable about gdbserver should ping me.
Andrew's the remote protocol guru, and I handle gdbserver; feel free to
ask anything. I imagine that adding a utility function somewhere to
read /proc/%d/auxv and a dispatch point in the target_ops structure is
all that it would take.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-01-30 19:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-29 2:59 Roland McGrath
2004-01-29 6:39 ` Eli Zaretskii
2004-01-29 8:20 ` Roland McGrath
2004-01-29 20:14 ` Eli Zaretskii
2004-01-29 21:31 ` Roland McGrath
2004-01-30 19:03 ` Daniel Jacobowitz [this message]
2004-01-30 23:35 ` Andrew Cagney
2004-01-30 23:51 ` Roland McGrath
2004-01-31 0:11 ` Andrew Cagney
2004-01-31 0:16 ` Roland McGrath
2004-02-02 14:27 ` Andrew Cagney
2004-02-17 16:35 ` Andrew Cagney
2004-02-18 2:08 ` Roland McGrath
2004-02-24 3:50 ` Roland McGrath
2004-02-25 3:59 ` Andrew Cagney
2004-03-19 0:09 ` [COMMITTED PATCH] testsuite for info auxv Roland McGrath
2004-03-17 20:46 ` Roland McGrath
2004-02-25 4:03 ` [PATCH] auxv support Daniel Jacobowitz
2004-02-25 20:38 ` Roland McGrath
[not found] <200401310013.i0V0DnGE018646@magilla.sf.frob.com>
2004-02-01 6:04 ` Daniel Jacobowitz
2004-02-01 22:36 ` Roland McGrath
2004-02-02 0:11 ` Roland McGrath
2004-02-02 6:24 ` Eli Zaretskii
2004-02-02 14:17 ` Andrew Cagney
2004-02-02 14:25 ` Andrew Cagney
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=20040130190357.GA18536@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