From: Andrew Cagney <cagney@gnu.org>
To: Roland McGrath <roland@redhat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] auxv support
Date: Mon, 02 Feb 2004 14:27:00 -0000 [thread overview]
Message-ID: <401E5E69.9020906@gnu.org> (raw)
In-Reply-To: <200401310016.i0V0G44M018660@magilla.sf.frob.com>
> Yes, it's a bug - GDB should correctly display the name of all auxv
>> entries for the system it is running on (if we don't do this, no one
>> will ever notice, and the auxv table will never be updated ;-).
>
>
> Ok, I can get behind that rationale.
>
>
>> If you can do this wow.
>>
>> Look at the
>
>
> Huh? Did a finger slip before you finished writing this message?
Yes, tipo, "Look at the" turned into the earlier paragraph pointing at
corefile.exp et.al.
Andrew
next prev parent reply other threads:[~2004-02-02 14:27 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
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 [this message]
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=401E5E69.9020906@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