public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/29790] [gdb/testsuite] FAIL: gdb.arch/i386-pkru.exp: read value after setting value
Date: Tue, 03 Jan 2023 15:41:10 +0000 [thread overview]
Message-ID: <bug-29790-4717-h6jHm9aD2X@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29790-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29790
--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b46632ca16021962c33c2ea32b8104fd258ef0af
commit b46632ca16021962c33c2ea32b8104fd258ef0af
Author: Tom de Vries <tdevries@suse.de>
Date: Tue Jan 3 16:41:05 2023 +0100
[gdb/testsuite] Add xfail in gdb.arch/i386-pkru.exp
On a x86_64-linux machine with pkru register, I run into:
...
(gdb) PASS: gdb.arch/i386-pkru.exp: set pkru value
info register pkru^M
pkru 0x12345678 305419896^M
(gdb) FAIL: gdb.arch/i386-pkru.exp: read value after setting value
...
This is a regression due to kernel commit e84ba47e313d ("x86/fpu: Hook up
PKRU
onto ptrace()"). This is fixed by recent kernel commit 4a804c4f8356
("x86/fpu: Allow PKRU to be (once again) written by ptrace.").
The regression occurs for kernel versions v5.14-rc1 (the first tag
containing
the regression) up to but excluding v6.2-rc1 (the first tag containing the
fix).
Fix this by adding an xfail for the appropriate kernel versions.
Tested on x86_64-linux.
PR testsuite/29790
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29790
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-01-03 15:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 14:03 [Bug tdep/29790] New: [gdb] " vries at gcc dot gnu.org
2022-11-17 7:33 ` [Bug tdep/29790] " vries at gcc dot gnu.org
2022-12-16 22:30 ` vries at gcc dot gnu.org
2023-01-02 10:07 ` vries at gcc dot gnu.org
2023-01-02 10:07 ` [Bug testsuite/29790] " vries at gcc dot gnu.org
2023-01-02 10:07 ` [Bug testsuite/29790] [gdb/testsuite] " vries at gcc dot gnu.org
2023-01-03 15:41 ` cvs-commit at gcc dot gnu.org [this message]
2023-01-03 15:42 ` vries at gcc dot gnu.org
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=bug-29790-4717-h6jHm9aD2X@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).