From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@mvista.com>, Roland McGrath <roland@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] auxv support
Date: Fri, 30 Jan 2004 23:35:00 -0000 [thread overview]
Message-ID: <401AE965.7020302@gnu.org> (raw)
In-Reply-To: <20040130190357.GA18536@nevyn.them.org>
> Since Andrew submitted a previous patch for the same feature, I'd
> appreciate it if he would look over this also.
The target vector update is fine.
Roland,
Would you be able to also knock up an "auxv.exp" test case? Something
to run the command and, most notably, fail if "???" comes out as the
auxv entry name?
Also, just file a bug reports that there isn't an equivalent MI auxv
command, and that those other commands need need documenting. I'll (or
someone) will need to come back to that.
Andrew
next prev parent reply other threads:[~2004-01-30 23:35 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
2004-01-30 23:35 ` Andrew Cagney [this message]
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=401AE965.7020302@gnu.org \
--to=cagney@gnu.org \
--cc=drow@mvista.com \
--cc=gdb-patches@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