Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis <luis.machado.foss@gmail.com>
To: Matthieu Longo <matthieu.longo@arm.com>
Cc: Thiago Jung Bauermann <thiago.bauermann@linaro.org>,
	Luis Machado <luis.machado@amd.com>,  Tom Tromey <tom@tromey.com>,
	Andrew Burgess <aburgess@redhat.com>,
	gdb-patches@sourceware.org
Subject: Re: [PATCH v3] gdb: align siginfo_t with the Linux kernel definition
Date: Tue, 21 Jul 2026 10:23:36 +0100	[thread overview]
Message-ID: <CANnS9rtqu91-KENRU2+PF-LO4hbsLWQ4x-QFZ6Vg5sMDzGOBMQ@mail.gmail.com> (raw)
In-Reply-To: <6abf57b5-831c-4b4b-850a-d46e7292b578@arm.com>

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

Hi Matthieu,

Bear with me as I go through this one and I can share some feedback/updates.

On Tue, Jul 21, 2026, 10:19 Matthieu Longo <matthieu.longo@arm.com> wrote:

> On 08/07/2026 16:54, Matthieu Longo wrote:
> > On 02/07/2026 17:52, Matthieu Longo wrote:
> >> GDB's current definition of siginfo_t is missing many fields present in
> >> the Linux kernel definition [1].
> >>
> >> These fields are useful for providing detailed, user-friendly
> diagnostics
> >> when a fault occurs. Some new AArch64 extensions, such as Permission
> >> Overlay Enhancement used to implement Protection Keys [2], require the
> >> debugger to inspect 'si_pkey' alongside 'si_addr' to help the user
> identify
> >> the problematic key.
> >>
> >> This patch aligns GDB's definition of the __sifields._sigfault member of
> >> siginfo_t with the definition from the Linux kernel master branch.
> >>
> >> [1]:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
> >>      tree/include/uapi/asm-generic/siginfo.h#n69
> >> [2]:
> https://lore.kernel.org/all/20160212210213.ABC488FA@viggo.jf.intel.com/
> >>
> >> Reviewed-by: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
> >> ---
> > Ping
>
> Hi Thiago,
>
> Please can you advise ?
> I haven't manage to get any approval from maintainers up until now.
>
> Matthieu
>

[-- Attachment #2: Type: text/html, Size: 2217 bytes --]

  reply	other threads:[~2026-07-21  9:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-02 16:52 Matthieu Longo
2026-07-08 15:54 ` Matthieu Longo
2026-07-21  9:17   ` Matthieu Longo
2026-07-21  9:23     ` Luis [this message]
2026-07-21 21:09 ` Luis
2026-07-22 15:00   ` Matthieu Longo
2026-07-22 23:09     ` Luis
2026-07-24  9:18       ` Matthieu Longo
2026-07-24  9:42         ` Matthieu Longo
2026-07-25  7:46         ` Luis
2026-07-26  5:12           ` Maciej W. Rozycki
2026-07-27 12:23           ` Matthieu Longo

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=CANnS9rtqu91-KENRU2+PF-LO4hbsLWQ4x-QFZ6Vg5sMDzGOBMQ@mail.gmail.com \
    --to=luis.machado.foss@gmail.com \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=luis.machado@amd.com \
    --cc=matthieu.longo@arm.com \
    --cc=thiago.bauermann@linaro.org \
    --cc=tom@tromey.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