Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [committed][gdb/tdep] Handle si_addr_bnd in compat_siginfo_from_siginfo
Date: Mon, 18 Jan 2021 09:35:35 +0100	[thread overview]
Message-ID: <8d3ff00d-0cf3-51fc-da81-c1150aef112c@suse.de> (raw)
In-Reply-To: <20210111103255.GA540@delia>

[-- Attachment #1: Type: text/plain, Size: 1047 bytes --]

On 1/11/21 11:32 AM, Tom de Vries wrote:
> Hi,
> 
> When running test-case gdb.arch/i386-mpx-sigsegv.exp with target board
> unix/-m32, we run into:
> ...
> (gdb) continue^M
> Continuing.^M
> Saw a #BR! status 1 at 0x8048c2d^M
> ^M
> Program received signal SIGSEGV, Segmentation fault^M
> Upper bound violation while accessing address 0x0804c15c^M
> Bounds: [lower = 0x00000000, upper = 0x00000000].^M
> 0x08048a4f in lower (p=0x804c160, a=0x804c180, b=0x804c1a0, c=0x804c1c0, \
>   d=0x804c1e0, len=1) at i386-mpx-sigsegv.c:79^M
> 79        value = *(p - len);^M
> (gdb) FAIL: gdb.arch/i386-mpx-sigsegv.exp: MPX signal segv Lower: 0
> ...
> 
> The problem is that lower and upper in the Bounds message are 0x0, which is
> caused by $_siginfo._sifields._sigfault._addr_bnd.{_lower,_upper} evaluating
> to 0x0.
> 
> Fix this by copying the si_lower/si_upper fields in
> compat_siginfo_from_siginfo.
> 
> Tested on x86_64-linux, with target board unix/-m32.
> 
> Any comments?
> 

Added SEGV_BNDERR define, and committed as below.

Thanks,
- Tom



[-- Attachment #2: 0001-gdb-tdep-Handle-si_addr_bnd-in-compat_siginfo_from_siginfo.patch --]
[-- Type: text/x-patch, Size: 2679 bytes --]

[gdb/tdep] Handle si_addr_bnd in compat_siginfo_from_siginfo

When running test-case gdb.arch/i386-mpx-sigsegv.exp with target board
unix/-m32, we run into:
...
(gdb) continue^M
Continuing.^M
Saw a #BR! status 1 at 0x8048c2d^M
^M
Program received signal SIGSEGV, Segmentation fault^M
Upper bound violation while accessing address 0x0804c15c^M
Bounds: [lower = 0x00000000, upper = 0x00000000].^M
0x08048a4f in lower (p=0x804c160, a=0x804c180, b=0x804c1a0, c=0x804c1c0, \
  d=0x804c1e0, len=1) at i386-mpx-sigsegv.c:79^M
79        value = *(p - len);^M
(gdb) FAIL: gdb.arch/i386-mpx-sigsegv.exp: MPX signal segv Lower: 0
...

The problem is that lower and upper in the Bounds message are 0x0, which is
caused by $_siginfo._sifields._sigfault._addr_bnd.{_lower,_upper} evaluating
to 0x0.

Fix this by copying the si_lower/si_upper fields in
compat_siginfo_from_siginfo.

Tested on x86_64-linux, with target board unix/-m32.

gdb/ChangeLog:

2021-01-11  Tom de Vries  <tdevries@suse.de>

	PR tdep/27172
	* nat/amd64-linux-siginfo.c (cpt_si_lower, cpt_si_upper, SEGV_BNDERR):
	New macro.
	(compat_siginfo_from_siginfo): Copy cpt_si_lower and cpt_si_upper
	for SEGV_BNDERR.

---
 gdb/nat/amd64-linux-siginfo.c | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/gdb/nat/amd64-linux-siginfo.c b/gdb/nat/amd64-linux-siginfo.c
index 8bcff454378..0c932814ec8 100644
--- a/gdb/nat/amd64-linux-siginfo.c
+++ b/gdb/nat/amd64-linux-siginfo.c
@@ -277,6 +277,8 @@ typedef struct compat_x32_siginfo
 #define cpt_si_ptr _sifields._rt._sigval.sival_ptr
 #define cpt_si_addr _sifields._sigfault._addr
 #define cpt_si_addr_lsb _sifields._sigfault._addr_lsb
+#define cpt_si_lower _sifields._sigfault.si_addr_bnd._lower
+#define cpt_si_upper _sifields._sigfault.si_addr_bnd._upper
 #define cpt_si_band _sifields._sigpoll._band
 #define cpt_si_fd _sifields._sigpoll._fd
 
@@ -290,6 +292,10 @@ typedef struct compat_x32_siginfo
 #define si_overrun si_timer2
 #endif
 
+#ifndef SEGV_BNDERR
+#define SEGV_BNDERR	3
+#endif
+
 /* The type of the siginfo object the kernel returns in
    PTRACE_GETSIGINFO.  If gdb is built as a x32 program, we get a x32
    siginfo.  */
@@ -324,6 +330,13 @@ compat_siginfo_from_siginfo (compat_siginfo_t *to, const siginfo_t *from)
       to->cpt_si_pid = from_ptrace.cpt_si_pid;
       to->cpt_si_uid = from_ptrace.cpt_si_uid;
     }
+  else if (to->si_code == SEGV_BNDERR
+	   && to->si_signo == SIGSEGV)
+    {
+      to->cpt_si_addr = from_ptrace.cpt_si_addr;
+      to->cpt_si_lower = from_ptrace.cpt_si_lower;
+      to->cpt_si_upper = from_ptrace.cpt_si_upper;
+    }
   else if (to->si_code < 0)
     {
       to->cpt_si_pid = from_ptrace.cpt_si_pid;

      reply	other threads:[~2021-01-18  8:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11 10:32 [PATCH][gdb/tdep] " Tom de Vries
2021-01-18  8:35 ` Tom de Vries [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=8d3ff00d-0cf3-51fc-da81-c1150aef112c@suse.de \
    --to=tdevries@suse.de \
    --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