From: <srinath.parvathaneni@arm.com>
To: <gdb-patches@sourceware.org>
Cc: <simark@simark.ca>, <luis.machado.foss@gmail.com>,
<thiago.bauermann@linaro.org>, <guinevere@redhat.com>,
<Ezra.Sitorus@arm.com>, <Matthieu.Longo@arm.com>,
<peter.maydell@linaro.org>,
Srinath Parvathaneni <srinath.parvathaneni@arm.com>
Subject: [PATCH v4 2/5] gdb: Improve SIGSEGV diagnostics for POE faults
Date: Tue, 1 Sep 2026 09:12:13 +0000 [thread overview]
Message-ID: <20260901091216.5711-3-srinath.parvathaneni@arm.com> (raw)
In-Reply-To: <20260901091216.5711-1-srinath.parvathaneni@arm.com>
[-- Attachment #1: Type: text/plain, Size: 614 bytes --]
When a SIGSEGV is caused by a Permission Overlay violation, include
additional information in GDB's error message to help identify the
failing address along with the responsible protection key causing
this fault.
Example:
(gdb) c
Continuing.
Program received signal SIGSEGV, Segmentation fault
Protection Key Violation while accessing address 0x0000fffff7ff3000 with Protection Key = 1.
0x0000aaaaaaaa0a3c in main () at poe_sigsegv.c:26
Approved-by: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
---
gdb/aarch64-linux-tdep.c | 21 ++++++++++++++++++---
1 file changed, 18 insertions(+), 3 deletions(-)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: v4-0002-PATCH-2-5-gdb-Improve-SIGSEGV-diagnostics-for-POE.patch --]
[-- Type: text/x-patch; name="v4-0002-PATCH-2-5-gdb-Improve-SIGSEGV-diagnostics-for-POE.patch", Size: 2678 bytes --]
diff --git a/gdb/aarch64-linux-tdep.c b/gdb/aarch64-linux-tdep.c
index 235b35bcfb4..1b2d4435088 100644
--- a/gdb/aarch64-linux-tdep.c
+++ b/gdb/aarch64-linux-tdep.c
@@ -53,6 +53,7 @@
#include "arch/aarch64-fpmr-linux.h"
#include "arch/aarch64-gcs-linux.h"
+#include "arch/aarch64-poe-linux.h"
#include "arch/aarch64-mte.h"
#include "arch/aarch64-mte-linux.h"
#include "arch/aarch64-pauth-linux.h"
@@ -2675,11 +2676,12 @@ aarch64_linux_report_signal_info (struct gdbarch *gdbarch,
{
aarch64_gdbarch_tdep *tdep = gdbarch_tdep<aarch64_gdbarch_tdep> (gdbarch);
- if (!(tdep->has_mte () || tdep->has_gcs ()) || siggnal != GDB_SIGNAL_SEGV)
+ if (!(tdep->has_mte () || tdep->has_gcs () || tdep->has_poe ())
+ || siggnal != GDB_SIGNAL_SEGV)
return;
CORE_ADDR fault_addr = 0;
- long si_code = 0, si_errno = 0;
+ long si_code = 0, si_errno = 0, si_pkey = -1;
try
{
@@ -2689,6 +2691,8 @@ aarch64_linux_report_signal_info (struct gdbarch *gdbarch,
violation. */
si_code = parse_and_eval_long (gdb_si::get (si_key::siginfo_code));
si_errno = parse_and_eval_long (gdb_si::get (si_key::siginfo_errno));
+ if (tdep->has_poe ())
+ si_pkey = parse_and_eval_long (gdb_si::get (si_key::siginfo_pkey));
fault_addr
= parse_and_eval_long (gdb_si::get (si_key::siginfo_addr));
@@ -2705,6 +2709,8 @@ aarch64_linux_report_signal_info (struct gdbarch *gdbarch,
meaning = _("Memory tag violation");
else if (si_code == AARCH64_SEGV_CPERR && si_errno == 0)
meaning = _("Guarded Control Stack error");
+ else if (si_code == AARCH64_SEGV_PKUERR)
+ meaning = _("Protection Key Violation");
else
return;
@@ -2736,6 +2742,15 @@ aarch64_linux_report_signal_info (struct gdbarch *gdbarch,
uiout->field_string ("logical-tag", hex_string (ltag));
}
}
+ /* Additional information for SIGSEGV caused by a permission overlay
+ violation. */
+ else if (si_code == AARCH64_SEGV_PKUERR)
+ {
+ uiout->text (_(" while accessing address "));
+ uiout->field_core_addr ("fault-addr", gdbarch, fault_addr);
+ uiout->text (_(" with Protection Key = "));
+ uiout->field_signed ("protection-key", si_pkey);
+ }
else if (si_code != AARCH64_SEGV_CPERR)
{
uiout->text ("\n");
@@ -3056,7 +3071,7 @@ aarch64_linux_init_abi (struct gdbarch_info info, struct gdbarch *gdbarch)
aarch64_linux_decode_memtag_section);
}
- if (tdep->has_mte () || tdep->has_gcs ())
+ if (tdep->has_mte () || tdep->has_gcs () || tdep->has_poe ())
set_gdbarch_report_signal_info (gdbarch, aarch64_linux_report_signal_info);
/* Initialize the aarch64_linux_record_tdep. */
next prev parent reply other threads:[~2026-09-01 9:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 9:12 [PATCH v4 0/5] gdb/aarch64: Add POR_EL0 register support for FEAT_S1POE srinath.parvathaneni
2026-09-01 9:12 ` [PATCH v4 1/5] " srinath.parvathaneni
2026-09-10 7:01 ` Thiago Jung Bauermann
2026-09-10 22:32 ` Thiago Jung Bauermann
2026-09-12 21:43 ` Luis
2026-09-01 9:12 ` srinath.parvathaneni [this message]
2026-09-01 9:12 ` [PATCH v4 3/5] gdbserver/aarch64: Add POR_EL0 register support srinath.parvathaneni
2026-09-01 9:12 ` [PATCH v4 4/5] gdb/aarch64: Add core file and signal frame support for FEAT_S1POE srinath.parvathaneni
2026-09-10 7:02 ` Thiago Jung Bauermann
2026-09-01 9:12 ` [PATCH v4 5/5] gdb/testsuite: Add FEAT_S1POE testcases srinath.parvathaneni
2026-09-10 7:13 ` Thiago Jung Bauermann
2026-09-07 12:52 ` [PATCH v4 0/5] gdb/aarch64: Add POR_EL0 register support for FEAT_S1POE Srinath Parvathaneni
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=20260901091216.5711-3-srinath.parvathaneni@arm.com \
--to=srinath.parvathaneni@arm.com \
--cc=Ezra.Sitorus@arm.com \
--cc=Matthieu.Longo@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=guinevere@redhat.com \
--cc=luis.machado.foss@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=simark@simark.ca \
--cc=thiago.bauermann@linaro.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