public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tom@tromey.com>
Cc: Hannes Domani via Gdb-patches <gdb-patches@sourceware.org>,
	Joel Brobecker <brobecker@adacore.com>
Subject: Re: [PATCH] Add _sigsys info to siginfo struct
Date: Sun, 16 Jan 2022 13:39:06 +0400	[thread overview]
Message-ID: <YePnunz8CYmQRffs@adacore.com> (raw)
In-Reply-To: <87y23nmxow.fsf@tromey.com>

> Hannes> This patch adds information about _sigsys structure from newer
> Hannes> kernels, so that $_siginfo decoding can show information about
> Hannes> _sigsys, making it easier for developers to debug seccomp failures.
> 
> I wonder if this is deserving of a NEWS entry.

Hmm, yeah; I think Tom is right, it does.

-- 
Joel

      reply	other threads:[~2022-01-16  9:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220103185854.1675-1-ssbssa.ref@yahoo.de>
2022-01-03 18:58 ` Hannes Domani
2022-01-08 11:03   ` Joel Brobecker
2022-01-08 12:34     ` Hannes Domani
2022-01-08 12:44       ` Joel Brobecker
2022-01-08 13:18         ` Hannes Domani
2022-01-10 15:12   ` Tom Tromey
2022-01-16  9:39     ` Joel Brobecker [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=YePnunz8CYmQRffs@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).