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] [intel Performance-core] FAIL: gdb.python/py-record-btrace.exp: prepare record: python insn = r.instruction_history
Date: Mon, 06 Feb 2023 14:05:54 +0000 [thread overview]
Message-ID: <bug-30075-4717-4fFnlguIS1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30075-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30075
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Without libipt, I run into different fails, on the other set of cores: the
efficiency-cores.
With taskset -c 0, I have:
...
$ taskset -c 0 gdb -q -batch
./outputs/gdb.python/py-record-btrace/py-record-btrace -ex "set trace-commands
on" -ex "display /i \$pc" -ex "start" -ex "record btrace bts" -ex "si 4" -ex
"record instruction-history"
+display /i $pc
+start
Temporary breakpoint 1 at 0x4004d1: file
/data/vries/gdb/src/gdb/testsuite/gdb.python/py-record-btrace.c, line 40.
Temporary breakpoint 1, main () at
/data/vries/gdb/src/gdb/testsuite/gdb.python/py-record-btrace.c:40
40 for (i = 0, j = 0; i < 100; ++i)
1: x/i $pc
=> 0x4004d1 <main+8>: movl $0x0,-0x4(%rbp)
+record btrace bts
+target record-btrace
+si 4
0x00000000004004f6 40 for (i = 0, j = 0; i < 100; ++i)
1: x/i $pc
=> 0x4004f6 <main+45>: jle 0x4004e1 <main+24>
+record instruction-history
1 0x00000000004004d1 <main+8>: movl $0x0,-0x4(%rbp)
2 0x00000000004004d8 <main+15>: movl $0x0,-0x8(%rbp)
3 0x00000000004004df <main+22>: jmp 0x4004f2 <main+41>
4 0x00000000004004f2 <main+41>: cmpl $0x63,-0x4(%rbp)
...
That looks reasonable.
With taskset -c 4, however:
...
$ taskset -c 4 ./gdb.sh -q -batch
./outputs/gdb.python/py-record-btrace/py-record-btrace -ex "set trace-commands
on" -ex "display /i \$pc" -ex "start" -ex "record btrace bts" -ex "si 4" -ex
"record instruction-history"
+display /i $pc
+start
Temporary breakpoint 1 at 0x4004d1: file
/data/vries/gdb/src/gdb/testsuite/gdb.python/py-record-btrace.c, line 40.
Temporary breakpoint 1, main () at
/data/vries/gdb/src/gdb/testsuite/gdb.python/py-record-btrace.c:40
40 for (i = 0, j = 0; i < 100; ++i)
1: x/i $pc
=> 0x4004d1 <main+8>: movl $0x0,-0x4(%rbp)
+record btrace bts
+target record-btrace
+si 4
0x00000000004004f6 40 for (i = 0, j = 0; i < 100; ++i)
1: x/i $pc
=> 0x4004f6 <main+45>: jle 0x4004e1 <main+24>
+record instruction-history
1 0x00000000004004d1 <main+8>: movl $0x0,-0x4(%rbp)
2 0x00000000004004d8 <main+15>: movl $0x0,-0x8(%rbp)
3 0x00000000004004df <main+22>: jmp 0x4004f2 <main+41>
4 0x00000000004004e1 <main+24>: mov -0x8(%rbp),%eax
5 0x00000000004004e4 <main+27>: mov %eax,%edi
6 0x00000000004004e6 <main+29>: call 0x4004a7 <function>
7 0x00000000004004eb <main+34>: mov %eax,-0x8(%rbp)
8 0x00000000004004ee <main+37>: addl $0x1,-0x4(%rbp)
9 0x00000000004004f2 <main+41>: cmpl $0x63,-0x4(%rbp)
...
That makes no sense as instruction history, this is just disassembly.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-06 14:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 12:24 [Bug record/30075] New: " vries at gcc dot gnu.org
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 [this message]
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-4fFnlguIS1@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).