public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/29790] New: [gdb] FAIL: gdb.arch/i386-pkru.exp: read value after setting value
Date: Wed, 16 Nov 2022 14:03:20 +0000	[thread overview]
Message-ID: <bug-29790-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=29790

            Bug ID: 29790
           Summary: [gdb] FAIL: gdb.arch/i386-pkru.exp: read value after
                    setting value
           Product: gdb
           Version: 12.1
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tdep
          Assignee: unassigned at sourceware dot org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

Once in a blue moon, our OBS runs on a machine with pkru support, and I got
(with a gdb 12.1-based package):
...
Running
/home/abuild/rpmbuild/BUILD/gdb-12.1/gdb/testsuite/gdb.arch/i386-pkru.exp ...
PASS: gdb.arch/i386-pkru.exp: probe PKRU support
PASS: gdb.arch/i386-pkru.exp: pkru register
PASS: gdb.arch/i386-pkru.exp: continue to breakpoint: break here 1
PASS: gdb.arch/i386-pkru.exp: read pkru register
PASS: gdb.arch/i386-pkru.exp: set pkru value
FAIL: gdb.arch/i386-pkru.exp: read value after setting value
PASS: gdb.arch/i386-pkru.exp: continue to breakpoint: break here 2
FAIL: gdb.arch/i386-pkru.exp: variable after reading pkru
...

In more detail:
...
(gdb) PASS: gdb.arch/i386-pkru.exp: read pkru register
print /x $pkru = 0x44444444^M
$3 = 0x44444444^M
(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
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2022-11-16 14:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16 14:03 vries at gcc dot gnu.org [this message]
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
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@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).