From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH/RFC] auxv entries
Date: Mon, 15 Sep 2008 00:34:00 -0000 [thread overview]
Message-ID: <1221438784.17278.18.camel@localhost.localdomain> (raw)
In-Reply-To: <200809142127.m8ELR9eX025288@brahms.sibelius.xs4all.nl>
(I'd really, really like to talk to the person who thought it would be a
good idea to make <ctrl>+<enter> a shortcut to send the message.)
El dom, 14-09-2008 a las 23:27 +0200, Mark Kettenis escribió:
> Many, if not all, processor-specific ELF ABI documents have the
> following definition of auxv entries:
>
> typedef struct
> {
> int a_type;
> union {
> long a_val;
> void *a_ptr;
> void (*a_fcn)();
> } a_un;
> } auxv_t;
I have this in <elf.h> in ppc64-linux:
typedef struct
{
uint64_t a_type; /* Entry type */
union
{
uint64_t a_val; /* Integer value */
/* We use to have pointer elements added here. We cannot do that,
though, since it does not work when using 32-bit definitions
on 64-bit platforms and vice versa. */
} a_un;
} Elf64_auxv_t;
So default_auxv_parse seems right to me.
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2008-09-15 0:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-14 21:27 Mark Kettenis
2008-09-15 0:28 ` Thiago Jung Bauermann
2008-09-15 0:34 ` Thiago Jung Bauermann [this message]
2008-09-15 9:21 ` Mark Kettenis
2008-09-15 20:23 ` Mark Kettenis
2008-09-15 21:14 ` Daniel Jacobowitz
2008-09-16 3:28 ` Thiago Jung Bauermann
2008-09-15 3:21 ` 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=1221438784.17278.18.camel@localhost.localdomain \
--to=bauerman@br.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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