From: Pedro Alves <palves@redhat.com>
To: Chris Webb <chris@arachsys.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Replace struct siginfo with siginfo_t
Date: Fri, 06 Jul 2012 13:02:00 -0000 [thread overview]
Message-ID: <4FF6E1B6.6020901@redhat.com> (raw)
In-Reply-To: <20120706124530.GG13885@arachsys.com>
On 07/06/2012 01:45 PM, Chris Webb wrote:
> Glibc 2.16.0 removes the undocumented definition of 'struct siginfo' from
> <bits/siginfo.h>. This struct is also available as the POSIX-defined
> siginfo_t, so replace all uses of struct siginfo with siginfo_t.
Thanks, but this was already fixed by:
2012-03-21 Thomas Schwinge <thomas@codesourcery.com>
* amd64-linux-nat.c (amd64_linux_siginfo_fixup): Use siginfo_t instead
of struct siginfo.
* arm-linux-nat.c (arm_linux_stopped_data_address): Likewise.
* ia64-linux-nat.c (ia64_linux_stopped_data_address): Likewise.
* linux-nat.c (linux_nat_siginfo_fixup, siginfo_fixup)
(linux_xfer_siginfo, linux_nat_set_siginfo_fixup)
(linux_nat_get_siginfo): Likewise.
* linux-nat.h (struct lwp_info, linux_nat_set_siginfo_fixup)
(linux_nat_get_siginfo): Likewise.
* linux-tdep.c (linux_get_siginfo_type): Likewise.
* ppc-linux-nat.c (ppc_linux_stopped_data_address): Likewise.
* procfs.c (gdb_siginfo_t): Likewise.
2012-03-21 Thomas Schwinge <thomas@codesourcery.com>
* linux-arm-low.c (arm_stopped_by_watchpoint): Use siginfo_t instead of
struct siginfo.
* linux-low.c (siginfo_fixup, linux_xfer_siginfo): Likewise.
* linux-x86-low.c (x86_siginfo_fixup): Likewise.
* linux-low.h: Include <signal.h>.
(struct siginfo): Remove forward declaration.
(struct linux_target_ops) <siginfo_fixup>: Use siginfo_t instead of
struct siginfo.
--
Pedro Alves
next prev parent reply other threads:[~2012-07-06 13:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 12:45 Chris Webb
2012-07-06 13:02 ` Pedro Alves [this message]
2012-07-06 13:10 ` Chris Webb
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=4FF6E1B6.6020901@redhat.com \
--to=palves@redhat.com \
--cc=chris@arachsys.com \
--cc=gdb-patches@sourceware.org \
/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