public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Luis Machado <luis.machado@arm.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Backporting minor fix to older gdb releases
Date: Tue, 14 Mar 2023 23:18:20 +0000	[thread overview]
Message-ID: <b2dc7c5f-d325-92ae-b000-ad6779dc1069@arm.com> (raw)

Hi,

I have a small issue (fixed in gdb 13 via commit 1ba3a3222039eb2576d29c9fd3af444f59fa51d2) that I'd like to backport
a fix to at least gdb 12 and gdb 11.

I did, however, notice that it is easily backportable to gdb 10 and gdb 9, versions also affected by the same bug.

Given the backport is small and helps prevent crashes when connecting to a QEMU that supports pointer authentication,
I'm wondering what global maintainers think about it.

If distros want to pick up the fix, they can do so without having to worry about conflicts.

What do you think?

Thanks,
Luis

             reply	other threads:[~2023-03-14 23:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14 23:18 Luis Machado [this message]
2023-03-15 11:33 ` Andrew Burgess
2023-03-15 12:26   ` Luis Machado
2023-03-15 13:11     ` Joel Brobecker
2023-03-15 13:45       ` Luis Machado
2023-03-20  4:18         ` Joel Brobecker
2023-03-22  9:57           ` Luis Machado
2023-04-11  6:04             ` Luis Machado

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=b2dc7c5f-d325-92ae-b000-ad6779dc1069@arm.com \
    --to=luis.machado@arm.com \
    --cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).