From: Tom de Vries <tdevries@suse.de>
To: Jan Beulich <jbeulich@suse.com>
Cc: John Baldwin <jhb@FreeBSD.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/testsuite] Fix gdb.arch/i386-signal.exp on x86_64
Date: Mon, 16 Oct 2023 10:23:22 +0200 [thread overview]
Message-ID: <243f409f-4e4a-4f95-8454-4e96f391efb4@suse.de> (raw)
In-Reply-To: <1141f1a0-0910-3194-6247-20a50b898d05@suse.com>
On 10/16/23 09:53, Jan Beulich wrote:
> On 07.10.2023 10:37, Tom de Vries wrote:
>> I've committed after adding a note about
>> https://sourceware.org/pipermail/binutils/2023-October/129818.html to
>> the commit log.
>
> Perhaps the better course of action would have been to backport
> fb1c10585ead to the respective gdb branch(es)?
The committed patch makes the gdb test-case robust against a problem in
a released gas version. So this is the right fix.
Backporting the gas fix to a gdb release branch has no effect for the
case that gas is build from binutils releases and branches.
Thanks,
- Tom
prev parent reply other threads:[~2023-10-16 8:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 11:14 Tom de Vries
2023-10-06 22:06 ` John Baldwin
2023-10-07 8:37 ` Tom de Vries
2023-10-16 7:53 ` Jan Beulich
2023-10-16 8:23 ` Tom de Vries [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=243f409f-4e4a-4f95-8454-4e96f391efb4@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.org \
--cc=jbeulich@suse.com \
--cc=jhb@FreeBSD.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).