From: Simon Sobisch <simonsobisch@gnu.org>
To: gdb@sourceware.org
Subject: How to use bts recording?
Date: Fri, 21 Jan 2022 16:18:06 +0100 [thread overview]
Message-ID: <40aebee9-d4ed-3a94-2341-cc17beeb6431@gnu.org> (raw)
(gdb) record btrace bts
Could not enable branch tracing for Thread 0x7ffff7fe6740 (LWP 2464935):
Failed to start recording: No such file or directory.
What does this message, raised by GDB 9.2, want to tell me?
Looks like GDB 11.1 is a bit better:
(gdb) record btrace bts
Could not enable branch tracing for Thread 0x7ffff7fe4740 (LWP 2756):
Failed to start recording: Operation not supported
How to get that operation working?
... still on the road to understand GDBs recording...
Simon
next reply other threads:[~2022-01-21 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 15:18 Simon Sobisch [this message]
[not found] ` <DM8PR11MB57499C939B8E0B461F7489ECDE5E9@DM8PR11MB5749.namprd11.prod.outlook.com>
[not found] ` <eabf7025-9866-fcb9-507e-a0e29c0970e9@gnu.org>
2022-01-24 9:27 ` Metzger, Markus T
2022-01-24 9:58 ` Simon Sobisch
2022-01-26 12:41 ` Metzger, Markus T
2022-01-26 16:40 ` Simon Sobisch
2022-01-26 17:11 ` Metzger, Markus T
2022-01-26 18:12 ` Simon Sobisch
2022-01-27 10:45 ` Metzger, Markus T
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=40aebee9-d4ed-3a94-2341-cc17beeb6431@gnu.org \
--to=simonsobisch@gnu.org \
--cc=gdb@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).