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/30073] [intel Efficient-core] FAIL: gdb.btrace/exception.exp: flat (pattern 1)
Date: Thu, 16 Feb 2023 13:32:56 +0000 [thread overview]
Message-ID: <bug-30073-4717-5lpQ9XL1MD@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30073-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30073
--- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Markus Metzger from comment #5)
> On my system, I do not get any BTS records on E-cores, and the perf event
> head pointer does not move. Looks like the BTS enable request gets stuck.
>
> Could you print the result of 'maint btrace packet-history 0, +100'?
I've build without libipt, ran the test-case gdb.btrace/exception.exp, copied
outputs/gdb.btrace/exception/gdb.in.2 to gdb.in, edited it like so:
...
$ cat gdb.in
set height 0
set width 0
dir
dir /data/vries/gdb/src/gdb/testsuite/gdb.btrace
file
/data/vries/gdb/leap-15-4/build/gdb/testsuite/outputs/gdb.btrace/exception/exception
delete breakpoints
info breakpoints
break -qualified main
run
set record function-call-history-size 0
break 56
break 59
continue
set record btrace bts buffer-size 128000
record btrace
continue
maint btrace packet-history 0, +100
#record function-call-history 1
#record function-call-history /c 1
...
and ran it:
...
$ gdb -q -batch -ex "set trace-commands on" -x gdb.in
+set height 0
+set width 0
+dir
+dir /data/vries/gdb/src/gdb/testsuite/gdb.btrace
+file
/data/vries/gdb/leap-15-4/build/gdb/testsuite/outputs/gdb.btrace/exception/exception
+delete breakpoints
+info breakpoints
No breakpoints or watchpoints.
+break -qualified main
Breakpoint 1 at 0x400768: file
/data/vries/gdb/src/gdb/testsuite/gdb.btrace/exception.cc, line 55.
+run
Breakpoint 1, main () at
/data/vries/gdb/src/gdb/testsuite/gdb.btrace/exception.cc:55
55 test ();
+set record function-call-history-size 0
+break 56
Breakpoint 2 at 0x40076d: file
/data/vries/gdb/src/gdb/testsuite/gdb.btrace/exception.cc, line 56.
+break 59
Breakpoint 3 at 0x400779: file
/data/vries/gdb/src/gdb/testsuite/gdb.btrace/exception.cc, line 59.
+continue
Breakpoint 2, main () at
/data/vries/gdb/src/gdb/testsuite/gdb.btrace/exception.cc:56
56 test (); /* bp.1 */
+set record btrace bts buffer-size 128000
+record btrace
+target record-btrace
+target record-btrace
+continue
Breakpoint 3, main () at
/data/vries/gdb/src/gdb/testsuite/gdb.btrace/exception.cc:59
59 return ret; /* bp.2 */
+maint btrace packet-history 0, +100
No trace.
...
I hope that answers your question.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-16 13:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 9:26 [Bug record/30073] New: " vries at gcc dot gnu.org
2023-02-03 9:26 ` [Bug record/30073] " vries at gcc dot gnu.org
2023-02-03 9:28 ` vries at gcc dot gnu.org
2023-02-06 12:30 ` vries at gcc dot gnu.org
2023-02-13 18:10 ` vries at gcc dot gnu.org
2023-02-14 11:01 ` vries at gcc dot gnu.org
2023-02-16 11:16 ` markus.t.metzger at intel dot com
2023-02-16 13:32 ` vries at gcc dot gnu.org [this message]
2023-02-16 13:54 ` markus.t.metzger at intel dot com
2023-02-16 14:28 ` vries at gcc dot gnu.org
2023-02-16 14:52 ` markus.t.metzger at intel dot com
2023-02-16 16:00 ` 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-30073-4717-5lpQ9XL1MD@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).