From: Keith Seitz <keiths@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix gstack issues
Date: Sat, 29 Mar 2025 16:44:55 -0700 [thread overview]
Message-ID: <4554e169-76c6-46ab-93e2-089f9e36a128@redhat.com> (raw)
In-Reply-To: <87y0wp56id.fsf@tromey.com>
On 3/28/25 11:56 AM, Tom Tromey wrote:
>>>>>> "Keith" == Keith Seitz <keiths@redhat.com> writes:
>
> Keith> BTW, Gwen raises the question: Is this something we want to include
> Keith> for 16.3?
>
> It's fine by me, I think it's safe & fixes a real bug.
> You'll have to file it in bugzilla to do that.
I neglected to mention it, but I filed gdb/32828 for this.
Keith
next prev parent reply other threads:[~2025-03-29 23:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 15:54 Keith Seitz
2025-03-27 18:02 ` Guinevere Larsen
2025-03-27 18:15 ` Tom Tromey
2025-03-28 15:17 ` Keith Seitz
2025-03-28 16:25 ` Keith Seitz
2025-03-28 18:56 ` Tom Tromey
2025-03-29 23:44 ` Keith Seitz [this message]
2025-03-28 18:57 ` Sam James
2025-03-28 21:33 ` Keith Seitz
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=4554e169-76c6-46ab-93e2-089f9e36a128@redhat.com \
--to=keiths@redhat.com \
--cc=gdb-patches@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