From: Andrew Burgess <aburgess@redhat.com>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/tdep] Backport i386_canonicalize_syscall rewrite to gdb-16-branch
Date: Thu, 13 Mar 2025 15:09:36 +0000 [thread overview]
Message-ID: <87frjhx8zz.fsf@redhat.com> (raw)
In-Reply-To: <20250313095325.23876-1-tdevries@suse.de>
Tom de Vries <tdevries@suse.de> writes:
> Commit fbfb29b304e ("[gdb/tdep] Rewrite i386_canonicalize_syscall") fixes
> PR32770, which reproduces on the gdb-16-branch, but the commit is not ideal
> for backporting because it completely rewrites i386_canonicalize_syscall.
>
> Instead, this is a version of the patch that adds a single line entry for each
> syscall value for which i386_canonicalize_syscall gives a different result
> with and without the patch.
>
> Consequently, the two versions give identical results. I've checked this for
> syscalls 0 to 466.
Given you've shown that this is equivalent to the version in
fbfb29b304e, and having taken a look at that commit, I'd be just as
happy to see that commit merged into the gdb-16-branch. The patch isn't
small, but equally, it's pretty contained and straight forward, so I
don't see huge risk there.
But if you're happier with this approach in the gdb-16-branch, that's
fine with me.
Approved-By: Andrew Burgess <aburgess@redhat.com>
Thanks,
Andrew
>
> Tested on x86_64-linux with target board unix/-m32, on top of gdb-16-branch.
>
> PR tdep/32770
> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=32770
next prev parent reply other threads:[~2025-03-13 15:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 9:53 Tom de Vries
2025-03-13 12:40 ` Guinevere Larsen
2025-03-13 13:06 ` Tom de Vries
2025-03-13 15:20 ` Guinevere Larsen
2025-03-13 15:35 ` Tom de Vries
2025-03-13 15:09 ` Andrew Burgess [this message]
2025-03-14 15:46 ` Tom de Vries
2025-03-14 15:50 ` Guinevere Larsen
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=87frjhx8zz.fsf@redhat.com \
--to=aburgess@redhat.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