From: Roland McGrath <roland@redhat.com>
To: Eli Zaretskii <eliz@elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] auxv support
Date: Thu, 29 Jan 2004 21:31:00 -0000 [thread overview]
Message-ID: <200401292131.i0TLVMS4003786@magilla.sf.frob.com> (raw)
In-Reply-To: Eli Zaretskii's message of Thursday, 29 January 2004 21:01:44 +0200 <3405-Thu29Jan2004210144+0200-eliz@elta.co.il>
> Thanks, I'm happy with this patch. Pwerhaps just point the user to a
> man page or an Info file, if any, where the system-specific details
> of the displayed infor could be found.
There isn't one. These bits are really at the level of implementation
detail. They are not really part of any spec I'm aware of per se (though
how and where to find them are centrally specified), just part of the local
contract between a kernel and system libraries.
next prev parent reply other threads:[~2004-01-29 21:31 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 [this message]
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
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=200401292131.i0TLVMS4003786@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=eliz@elta.co.il \
--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