Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
To: <srinath.parvathaneni@arm.com>
Cc: <gdb-patches@sourceware.org>,  <simark@simark.ca>,
	<luis.machado.foss@gmail.com>,  <guinevere@redhat.com>,
	<Ezra.Sitorus@arm.com>,  <Matthieu.Longo@arm.com>,
	<peter.maydell@linaro.org>
Subject: Re: [PATCH v4 5/5] gdb/testsuite: Add FEAT_S1POE testcases
Date: Thu, 10 Sep 2026 07:13:18 +0000	[thread overview]
Message-ID: <87zexpo9yp.fsf@linaro.org> (raw)
In-Reply-To: <20260901091216.5711-6-srinath.parvathaneni@arm.com> (srinath parvathaneni's message of "Tue, 1 Sep 2026 09:12:16 +0000")

<srinath.parvathaneni@arm.com> writes:

> Add testcases for POR_EL0 register access, POE pseudo-register access, SIGSEGV
> diagnostics, fix-and-continue support (updating $por_el0 after SIGSEGV and
> continuing with signal 0), core file support and the test for signal frame
> unwinding support.
> ---
>  gdb/testsuite/gdb.arch/aarch64-poe-core.exp   | 101 ++++++++++++++++++
>  gdb/testsuite/gdb.arch/aarch64-poe-sigframe.c |  45 ++++++++
>  .../gdb.arch/aarch64-poe-sigframe.exp         |  55 ++++++++++
>  gdb/testsuite/gdb.arch/aarch64-poe-sigsegv.c  |  52 +++++++++
>  .../gdb.arch/aarch64-poe-sigsegv.exp          |  55 ++++++++++
>  gdb/testsuite/gdb.arch/aarch64-poe.c          |  29 +++++
>  gdb/testsuite/gdb.arch/aarch64-poe.exp        |  60 +++++++++++
>  gdb/testsuite/lib/gdb.exp                     |  55 ++++++++++
>  8 files changed, 452 insertions(+)
>  create mode 100644 gdb/testsuite/gdb.arch/aarch64-poe-core.exp
>  create mode 100644 gdb/testsuite/gdb.arch/aarch64-poe-sigframe.c
>  create mode 100644 gdb/testsuite/gdb.arch/aarch64-poe-sigframe.exp
>  create mode 100644 gdb/testsuite/gdb.arch/aarch64-poe-sigsegv.c
>  create mode 100644 gdb/testsuite/gdb.arch/aarch64-poe-sigsegv.exp
>  create mode 100644 gdb/testsuite/gdb.arch/aarch64-poe.c
>  create mode 100644 gdb/testsuite/gdb.arch/aarch64-poe.exp

Thank you for writing the new sigframe test.

Approved-by: Thiago Jung Bauermann <thiago.bauermann@linaro.org>

-- 
Thiago
(he/him)

  reply	other threads:[~2026-09-10  7: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 ` [PATCH v4 2/5] gdb: Improve SIGSEGV diagnostics for POE faults srinath.parvathaneni
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 [this message]
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=87zexpo9yp.fsf@linaro.org \
    --to=thiago.bauermann@linaro.org \
    --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=srinath.parvathaneni@arm.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