[Bug record/19297] Internal error on "record btrace": Unexpected branch trace format.

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=19297

--- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Markus Metzger <mmetzger@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=46a3515b49ce30315e2b621525b29cd8263aed15

commit 46a3515b49ce30315e2b621525b29cd8263aed15
Author: Markus Metzger <markus.t.metzger@intel.com>
Date:   Thu Nov 19 14:33:41 2015 +0100

    btrace: diagnose "record btrace pt" without libipt

    If GDB has been configured without libipt support, i.e. HAVE_LIBIPT is
    undefined, and is running on a system that supports Intel(R) Processor
Trace,
    GDB will run into an internal error when trying to decode the trace.

        (gdb) record btrace
        (gdb) s
        usage (name=0x7fffffffe954 "fib-64")
            at src/fib.c:12
        12          fprintf(stderr, "usage: %s <num>\n", name);
        (gdb) info record
        Active record target: record-btrace
        Recording format: Intel(R) Processor Trace.
        Buffer size: 16kB.
        gdb/btrace.c:971: internal-error: Unexpected branch trace format.
        A problem internal to GDB has been detected,
        further debugging may prove unreliable.
        Quit this debugging session? (y or n)

    This requires a system with Linux kernel 4.1 or later running on a 5th
    Generation Intel Core processor or later.

    The issue is documented as PR 19297.

    When trying to enable branch tracing, in addition to checking the target
    support for the requested branch tracing format, also check whether GDB
    supports. it.

    gdb/
        * btrace.c (btrace_enable): Check whether HAVE_LIBIPT is defined.

    testsuite/
        * lib/gdb.exp (skip_btrace_pt_tests): Check for a "GDB does not
        support" error.

-- 
You are receiving this mail because:
You are on the CC list for the bug.