From: Tom Tromey <tom@tromey.com>
To: tdevries via Gdb-patches <gdb-patches@sourceware.org>
Cc: tdevries <tdevries@suse.de>
Subject: Re: [PATCH] [gdb] Fix segfault during inferior call to ifunc
Date: Mon, 02 Jan 2023 07:41:35 -0700 [thread overview]
Message-ID: <874jt9knhc.fsf@tromey.com> (raw)
In-Reply-To: <1a76ba98dddbd6c3dad498332d56f78e@suse.de> (tdevries via Gdb-patches's message of "Tue, 27 Dec 2022 09:54:43 +0000")
>>>>> tdevries via Gdb-patches <gdb-patches@sourceware.org> writes:
> From 0832e20dde6ebe71a1245935f4a41308368b6094 Mon Sep 17 00:00:00 2001
> From: Andrew Burgess <aburgess@redhat.com>
> Date: Mon, 26 Dec 2022 09:03:19 +0100
> Subject: [PATCH] [gdb] Fix segfault during inferior call to ifunc
Thanks, this looks good to me.
> Note that this series (
> https://inbox.sourceware.org/gdb-patches/20221214033441.499512-1-simon.marchi@polymtl.ca/ )
> should address this problem, but this patch is a simpler fix which is easy to
> backport.
Indeed, and I think it should be put on the GDB 13 branch.
Tom
prev parent reply other threads:[~2023-01-02 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 9:54 tdevries
2023-01-02 14:41 ` Tom Tromey [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=874jt9knhc.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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).