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 record/30075] New: [intel Performance-core] FAIL: gdb.python/py-record-btrace.exp: prepare record: python insn = r.instruction_history
Date: Fri, 03 Feb 2023 12:24:37 +0000 [thread overview]
Message-ID: <bug-30075-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30075
Bug ID: 30075
Summary: [intel Performance-core] FAIL:
gdb.python/py-record-btrace.exp: prepare record:
python insn = r.instruction_history
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: record
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
The processor is a i7-1250U with 12 threads:
- 2 performance cores (I guess providing 2 threads per core), and
- 8 efficient cores.
When using:
- taskset -c 0-3, the test-case fails
- taskset -c 4-11, the test-case passes
Fails like this:
...
(gdb) PASS: gdb.python/py-record-btrace.exp: prepare record: stepi 100
python insn = r.instruction_history^M
warning: Decode error (-20) at instruction 33 (offset = 0x3d69, pc = 0x400501):
compressed return without call.^M
(gdb) FAIL: gdb.python/py-record-btrace.exp: prepare record: python insn =
r.instruction_history
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-02-03 12:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 12:24 vries at gcc dot gnu.org [this message]
2023-02-04 20:13 ` [Bug record/30075] " vries at gcc dot gnu.org
2023-02-06 14:05 ` vries at gcc dot gnu.org
2023-02-06 15:02 ` vries at gcc dot gnu.org
2023-02-07 11:35 ` vries at gcc dot gnu.org
2023-02-07 12:03 ` vries at gcc dot gnu.org
2023-02-07 12:05 ` markus.t.metzger at intel dot com
2023-02-07 12:08 ` markus.t.metzger at intel dot com
2023-02-09 10:46 ` markus.t.metzger at intel dot com
2023-02-09 12:15 ` vries at gcc dot gnu.org
2023-02-13 18:10 ` vries at gcc dot gnu.org
2023-02-14 12:15 ` cvs-commit at gcc dot gnu.org
2023-02-14 12:16 ` [Bug testsuite/30075] " 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-30075-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).