From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: pedro@codesourcery.com
Cc: dje@google.com, gdb@sourceware.org
Subject: Re: new siginfo support doesn't build on glibc 2.2.2
Date: Tue, 10 Feb 2009 10:08:00 -0000 [thread overview]
Message-ID: <200902101006.n1AA6Xgq012736@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <200902092255.03612.pedro@codesourcery.com> (message from Pedro Alves on Mon, 9 Feb 2009 22:55:03 +0000)
> From: Pedro Alves <pedro@codesourcery.com>
> Date: Mon, 9 Feb 2009 22:55:03 +0000
>
> On Monday 09 February 2009 21:07:41, Doug Evans wrote:
> > fyi, glibc 2.2.2 doesn't have si_timerid, si_overrun. compilation of
> > amd64-linux-nat.c fails.
>
> Bummer. According to sigaction(2), those exist only since kernel
> 2.6. Those are defines, we could #ifdef on them, assuming we're
> ok with a gdb built on that platform and then moved to some more
> recent glibc will not translate those fields.
Isn't it fun having an OS where the kernel and C library are seperate
projects that are hardy ever fully in sync?
> I don't know if the siginfo layout in that version is the same
> as defined by the gdbarch callback, or even if your glibc's siginfo_t
> declaration matches your kernel's siginfo_t object layout --- there's
> a history of breakage on these matters.
I doubt there is actual breakage. The total size of siginfo_t should
not have changed between kernel releases. What may have happened is
that there have been new structs added to the union part of siginfo_t,
or that existing structs in there have been extended.
prev parent reply other threads:[~2009-02-10 10:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 21:07 Doug Evans
2009-02-09 22:55 ` Pedro Alves
2009-02-10 10:08 ` Mark Kettenis [this message]
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=200902101006.n1AA6Xgq012736@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=dje@google.com \
--cc=gdb@sourceware.org \
--cc=pedro@codesourcery.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