From: Walfred Tedeschi <walfred.tedeschi@intel.com>
To: palves@redhat.com, eliz@gnu.org, brobecker@adacore.com
Cc: gdb-patches@sourceware.org,
Walfred Tedeschi <walfred.tedeschi@intel.com>
Subject: [PATCH V5 0/5] Intel MPX bound violation support
Date: Fri, 22 Jan 2016 15:36:00 -0000 [thread overview]
Message-ID: <1453474456-13169-1-git-send-email-walfred.tedeschi@intel.com> (raw)
Hello all,
Thanks for the review!
First 4 patches are preparation on the siginfo type and
siginfo handling. Including the addition of new fields
related to the bound violation.
Last patch is the handler for the bound violation itself.
From V4 to V5:
* GDB and gdbserver siginfo fixup was aproved (not present here)
* Added Pedro's and Eli's feedback for all patches.
* Changed documentation section for bound violations.
* Changed bound violation output.
Thanks Pedro and Eli for the feedback and
sorry for submitting new revision without
adressing the issues.
Feedback e-mails ended up in not expected folder. :(
Sorry again for any inconvenience.
Thanks for the review and regards,
-Fred
Walfred Tedeschi (5):
Preparation for new siginfo on Linux
Use linux_get_siginfo_type_with_fields for x86
Add bound related fields to the siginfo structure
Adaptation of siginfo fixup for the new bnd fields
ntel MPX bound violation handling
gdb/NEWS | 15 ++
gdb/amd64-linux-tdep.c | 4 +
gdb/doc/gdb.texinfo | 25 ++
gdb/gdbarch.c | 32 +++
gdb/gdbarch.h | 11 +
gdb/gdbarch.sh | 6 +
gdb/i386-linux-tdep.c | 54 ++++
gdb/i386-linux-tdep.h | 8 +
gdb/i386-tdep.c | 4 +-
gdb/i386-tdep.h | 2 +
gdb/infrun.c | 34 +++
gdb/linux-tdep.c | 34 ++-
gdb/linux-tdep.h | 16 ++
gdb/nat/amd64-linux-siginfo.c | 312 ++++++++++++++++--------
gdb/nat/amd64-linux-siginfo.h | 16 +-
gdb/testsuite/gdb.arch/i386-mpx-sigsegv.c | 120 +++++++++
gdb/testsuite/gdb.arch/i386-mpx-sigsegv.exp | 88 +++++++
gdb/testsuite/gdb.arch/i386-mpx-simple_segv.c | 66 +++++
gdb/testsuite/gdb.arch/i386-mpx-simple_segv.exp | 125 ++++++++++
19 files changed, 862 insertions(+), 110 deletions(-)
create mode 100644 gdb/testsuite/gdb.arch/i386-mpx-sigsegv.c
create mode 100644 gdb/testsuite/gdb.arch/i386-mpx-sigsegv.exp
create mode 100644 gdb/testsuite/gdb.arch/i386-mpx-simple_segv.c
create mode 100644 gdb/testsuite/gdb.arch/i386-mpx-simple_segv.exp
--
2.1.4
next reply other threads:[~2016-01-22 15:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 15:36 Walfred Tedeschi [this message]
2016-01-22 15:17 ` [PATCH V5 4/5] Adaptation of siginfo fixup for the new bnd fields Walfred Tedeschi
2016-01-28 12:37 ` Pedro Alves
2016-02-02 10:31 ` Pedro Alves
2016-02-02 13:58 ` Walfred Tedeschi
2016-01-22 15:17 ` [PATCH V5 3/5] Add bound related fields to the siginfo structure Walfred Tedeschi
2016-01-28 12:23 ` Pedro Alves
2016-01-22 15:17 ` [PATCH V5 1/5] Preparation for new siginfo on Linux Walfred Tedeschi
2016-01-28 12:20 ` Pedro Alves
2016-01-22 15:18 ` [PATCH V5 5/5] ntel MPX bound violation handling Walfred Tedeschi
2016-01-28 13:43 ` Pedro Alves
2016-01-28 13:49 ` Walfred Tedeschi
2016-01-28 14:18 ` Pedro Alves
2016-02-02 10:09 ` Walfred Tedeschi
2016-02-02 10:38 ` Pedro Alves
2016-02-02 10:41 ` Walfred Tedeschi
2016-01-22 15:18 ` [PATCH V5 2/5] Use linux_get_siginfo_type_with_fields for x86 Walfred Tedeschi
2016-01-28 12:19 ` 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=1453474456-13169-1-git-send-email-walfred.tedeschi@intel.com \
--to=walfred.tedeschi@intel.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).