This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 1/5] configure: check for libipt
- From: Pedro Alves <palves at redhat dot com>
- To: Markus Metzger <markus dot t dot metzger at intel dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Tue, 30 Jun 2015 13:56:18 +0100
- Subject: Re: [PATCH 1/5] configure: check for libipt
- Authentication-results: sourceware.org; auth=none
- References: <1435047418-21611-1-git-send-email-markus dot t dot metzger at intel dot com> <1435047418-21611-2-git-send-email-markus dot t dot metzger at intel dot com>
On 06/23/2015 09:16 AM, Markus Metzger wrote:
> Check for libipt, an Intel(R) Processor Trace decoder library. The sources
> can be found on github at:
>
> https://github.com/01org/processor-trace
>
> 2015-06-23 Markus Metzger <markus.t.metzger@intel.com>
>
> * configure.ac: Check for libipt
> * configure: Regenerate.
> * config.in: Regenerate.
> * Makefile.in (LIBIPT): New.
> (CLIBS): Add $LIBIPT.
OK.
Is the library host independent? That is, does it handle
host vs target endianness, integer types, etc.? E.g., is a big endian PPC
host debugging against an x86-64 gdbserver able to use libipt? Another
example would be a big endian PPC host loading an x86-64 core dump that
includes ipt data (once we get to it).
Thanks,
Pedro Alves