From: Pedro Alves <palves@redhat.com>
To: Walfred Tedeschi <walfred.tedeschi@intel.com>,
eliz@gnu.org, brobecker@adacore.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH V4 1/6] Merge gdb and gdbserver implementations for siginfo
Date: Thu, 21 Jan 2016 15:05:00 -0000 [thread overview]
Message-ID: <56A0F3C2.4030305@redhat.com> (raw)
In-Reply-To: <1453387705-6597-2-git-send-email-walfred.tedeschi@intel.com>
On 01/21/2016 02:48 PM, Walfred Tedeschi wrote:
> Extract the compatible siginfo handling from amd64-linux-nat.c and
> gdbserver/linux-x86-low to a new file nat/amd64-linux-siginfo.c.
>
>
> 2016-01-15 Walfred Tedeschi <walfred.tedeschi@intel.com>
>
> gdb/ChangeLog:
>
> * nat/amd64-linux-siginfo.c: New file.
> * nat/amd64-linux-siginfo.h: New file.
> * Makefile.in (HFILES_NO_SRCDIR): Add nat/amd64-linux-siginfo.h.
> (amd64-linux-siginfo.o): New rule.
> * config/i386/linux64.mh (NATDEPFILES): Add amd64-linux-siginfo.o.
> * amd64-linux-nat.c (nat/amd64-linux-siginfo.h): New include.
> (compat_siginfo_from_siginfo, siginfo_from_compat_siginfo)
> (compat_x32_siginfo_from_siginfo, siginfo_from_compat_x32_siginfo)
> (compat_timeval, compat_sigval, compat_x32_clock, cpt_si_pid)
> (cpt_si_uid, cpt_si_timerid, cpt_si_overrun, cpt_si_status)
> (cpt_si_utime, cpt_si_stime, cpt_si_ptr, cpt_si_addr, cpt_si_band)
> (cpt_si_fd, si_timerid, si_overrun): Move to nat/amd64-linux-siginfo.c.
>
>
> gdb/gdbserver/ChangeLog:
>
> * configure.srv (x86_64-*-linux*): Add amd64-linux-siginfo.o
> to srv_tgtobj.
> (i[34567]86-*-linux*): Add amd64-linux-siginfo.o
> to srv_tgtobj.
> * linux-x86-low.c [__x86_64__]: Include
> "nat/amd64-linux-siginfo.h".
> (compat_siginfo_from_siginfo, siginfo_from_compat_siginfo)
> (compat_x32_siginfo_from_siginfo, siginfo_from_compat_x32_siginfo)
> (compat_timeval, compat_sigval, compat_x32_clock, cpt_si_pid)
> (cpt_si_uid, cpt_si_timerid, cpt_si_overrun, cpt_si_status)
> (cpt_si_utime, cpt_si_stime, cpt_si_ptr, cpt_si_addr, cpt_si_band)
> (cpt_si_fd, si_timerid, si_overrun): Move from
> nat/amd64-linux-siginfo.c.
> * Makefile.in (amd64-linux-siginfo.o:): New rule.
OK. This patch stands on its own -- please go ahead an push it.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-01-21 15:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 14:48 [PATCH V4 0/6] Intel MPX bound violation support Walfred Tedeschi
2016-01-21 14:48 ` [PATCH V4 3/6] Use linux_get_siginfo_type_with_fields for x86 Walfred Tedeschi
2016-01-21 14:49 ` [PATCH V4 5/6] Adaptation of siginfo fixup for the new bnd fields Walfred Tedeschi
2016-01-21 14:49 ` [PATCH V4 1/6] Merge gdb and gdbserver implementations for siginfo Walfred Tedeschi
2016-01-21 15:05 ` Pedro Alves [this message]
2016-01-21 14:49 ` [PATCH V4 4/6] Add bound related fields to the siginfo structure Walfred Tedeschi
2016-01-21 14:49 ` [PATCH V4 6/6] Intel MPX bound violation handling Walfred Tedeschi
2016-01-21 16:23 ` Eli Zaretskii
[not found] ` <AC542571535E904D8E8ADAE745D60B194452CD61@IRSMSX104.ger.corp.intel.com>
2016-01-21 17:34 ` FW: " Walfred Tedeschi
2016-01-21 17:51 ` Eli Zaretskii
2016-01-21 18:06 ` Pedro Alves
2016-01-21 18:22 ` Eli Zaretskii
2016-01-22 8:38 ` Walfred Tedeschi
2016-01-21 14:49 ` [PATCH V4 2/6] Prepararion for new siginfo on Linux Walfred Tedeschi
2016-01-21 15:05 ` Pedro Alves
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=56A0F3C2.4030305@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=walfred.tedeschi@intel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).