From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BEC373858C60; Thu, 16 Feb 2023 13:32:56 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BEC373858C60 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1676554376; bh=rfl0b7jkjK/9pV7/y0/fdglGU++RwGAYIAe6UORtQ6I=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Bnwh8/CeKsh50JTl41vPOF8Q8DPZuSuZeUJGHzZV1uvLe3xzmmTztK21I37oLEvtF kAuQTHw8aoRRzEISQHWcVohDcXUDZoN2Wr8WrQk/2OBbJh3+8UeiQmynfoB0K4dD2B Gh0VItoXhmU7dCblhEBokrZ5ApBe9N/oRiU+gky0= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug record/30073] [intel Efficient-core] FAIL: gdb.btrace/exception.exp: flat (pattern 1) Date: Thu, 16 Feb 2023 13:32:56 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: record X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30073 --- Comment #6 from Tom de Vries --- (In reply to Markus Metzger from comment #5) > On my system, I do not get any BTS records on E-cores, and the perf event > head pointer does not move. Looks like the BTS enable request gets stuck. >=20 > Could you print the result of 'maint btrace packet-history 0, +100'? I've build without libipt, ran the test-case gdb.btrace/exception.exp, copi= ed outputs/gdb.btrace/exception/gdb.in.2 to gdb.in, edited it like so: ... $ cat gdb.in set height 0 set width 0 dir dir /data/vries/gdb/src/gdb/testsuite/gdb.btrace file /data/vries/gdb/leap-15-4/build/gdb/testsuite/outputs/gdb.btrace/exception/= exception delete breakpoints info breakpoints break -qualified main run=20 set record function-call-history-size 0 break 56 break 59 continue set record btrace bts buffer-size 128000 record btrace continue maint btrace packet-history 0, +100 #record function-call-history 1 #record function-call-history /c 1 ... and ran it: ... $ gdb -q -batch -ex "set trace-commands on" -x gdb.in +set height 0 +set width 0 +dir +dir /data/vries/gdb/src/gdb/testsuite/gdb.btrace +file /data/vries/gdb/leap-15-4/build/gdb/testsuite/outputs/gdb.btrace/exception/= exception +delete breakpoints +info breakpoints No breakpoints or watchpoints. +break -qualified main Breakpoint 1 at 0x400768: file /data/vries/gdb/src/gdb/testsuite/gdb.btrace/exception.cc, line 55. +run=20 Breakpoint 1, main () at /data/vries/gdb/src/gdb/testsuite/gdb.btrace/exception.cc:55 55 test (); +set record function-call-history-size 0 +break 56 Breakpoint 2 at 0x40076d: file /data/vries/gdb/src/gdb/testsuite/gdb.btrace/exception.cc, line 56. +break 59 Breakpoint 3 at 0x400779: file /data/vries/gdb/src/gdb/testsuite/gdb.btrace/exception.cc, line 59. +continue Breakpoint 2, main () at /data/vries/gdb/src/gdb/testsuite/gdb.btrace/exception.cc:56 56 test (); /* bp.1 */ +set record btrace bts buffer-size 128000 +record btrace +target record-btrace +target record-btrace +continue Breakpoint 3, main () at /data/vries/gdb/src/gdb/testsuite/gdb.btrace/exception.cc:59 59 return ret; /* bp.2 */ +maint btrace packet-history 0, +100 No trace. ... I hope that answers your question. --=20 You are receiving this mail because: You are on the CC list for the bug.=