From: "Aktemur, Tankut Baris" <tankut.baris.aktemur@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:34:27 +0000 [thread overview]
Message-ID: <DM6PR11MB38848903BDD48A9449E0B9E5C45B9@DM6PR11MB3884.namprd11.prod.outlook.com> (raw)
In-Reply-To: <3c38a7e0-1ac5-4c76-2a9d-918cb7db9213@gnu.org>
On Friday, January 21, 2022 4:19 PM, Simon Sobisch wrote:
> (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?
Hi Simon,
You can build using the "--with-libipt-prefix" option when configuring GDB.
$ gdb/configure --help | grep libipt
--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)
-Baris
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
next prev parent reply other threads:[~2022-01-21 15:36 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 [this message]
2022-01-21 15:36 ` Willgerodt, Felix
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=DM6PR11MB38848903BDD48A9449E0B9E5C45B9@DM6PR11MB3884.namprd11.prod.outlook.com \
--to=tankut.baris.aktemur@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).