From: "Willgerodt, Felix" <felix.willgerodt@intel.com>
To: Simon Sobisch <simonsobisch@gnu.org>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: How to enable Intel Processor Trace support?
Date: Fri, 21 Jan 2022 15:36:05 +0000 [thread overview]
Message-ID: <MN2PR11MB45666A0CC9ADB8B077AC1B1C8E5B9@MN2PR11MB4566.namprd11.prod.outlook.com> (raw)
In-Reply-To: <3c38a7e0-1ac5-4c76-2a9d-918cb7db9213@gnu.org>
Hello Simon,
The documentation for all recording modes can be found here:
https://sourceware.org/gdb/onlinedocs/gdb/Process-Record-and-Replay.html
You can find the configure options for gdb in the configure script in the gdb folder.
You can pass all flags you find there to the top-level configure script.
For me gdb/configure --help shows these options:
--with-intel-pt include Intel Processor Trace support (auto/yes/no)
--with-libipt-prefix[=DIR] search for libipt in DIR/include and DIR/lib
--without-libipt-prefix don't search for libipt in includedir and libdir
--with-libipt-type=TYPE type of library to search for (auto/static/shared)
Regards,
Felix
> -----Original Message-----
> From: Gdb <gdb-bounces+felix.willgerodt=intel.com@sourceware.org> On
> Behalf Of Simon Sobisch via Gdb
> Sent: Freitag, 21. Januar 2022 16:19
> To: gdb@sourceware.org
> Subject: How to enable Intel Processor Trace support?
>
> (gdb) record btrace pt
> Intel Processor Trace support was disabled at compile time.
>
> I neither found a configure flag or a check for libipt - so how can I
> enable/disable this at compile time and where can I find that in the
> documentation?
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
prev parent reply other threads:[~2022-01-21 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 15:19 Simon Sobisch
2022-01-21 15:34 ` Aktemur, Tankut Baris
2022-01-21 15:36 ` Willgerodt, Felix [this message]
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=MN2PR11MB45666A0CC9ADB8B077AC1B1C8E5B9@MN2PR11MB4566.namprd11.prod.outlook.com \
--to=felix.willgerodt@intel.com \
--cc=gdb@sourceware.org \
--cc=simonsobisch@gnu.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).