From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 696053858D38; Mon, 6 Feb 2023 14:05:54 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 696053858D38 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1675692354; bh=mc8jN9yHvWPS/lJ3PPvjEgd3kfAgHCV+BdPROZs+aFE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=d7ZzkD1DkSis/Ro+yxn4v69YYE+ErO1vNjeWDet3N7j7r3rpBQPt1Od8UtCeJMmRk d3JhZZwTdoGLdcmKdFLQQFiFZ1VD7V2Y+VjsMnF2O9BE4NLEkQ9EIjjO9LSaWlL83f ZUvz8a2uJ6kQ+VcvtKU6feQufXTrmd3FBAgAyseo= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug record/30075] [intel Performance-core] FAIL: gdb.python/py-record-btrace.exp: prepare record: python insn = r.instruction_history Date: Mon, 06 Feb 2023 14:05:54 +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: HEAD 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=3D30075 --- Comment #1 from Tom de Vries --- Without libipt, I run into different fails, on the other set of cores: the efficiency-cores. With taskset -c 0, I have: ... $ taskset -c 0 gdb -q -batch ./outputs/gdb.python/py-record-btrace/py-record-btrace -ex "set trace-comma= nds on" -ex "display /i \$pc" -ex "start" -ex "record btrace bts" -ex "si 4" -= ex "record instruction-history" +display /i $pc +start Temporary breakpoint 1 at 0x4004d1: file /data/vries/gdb/src/gdb/testsuite/gdb.python/py-record-btrace.c, line 40. Temporary breakpoint 1, main () at /data/vries/gdb/src/gdb/testsuite/gdb.python/py-record-btrace.c:40 40 for (i =3D 0, j =3D 0; i < 100; ++i) 1: x/i $pc =3D> 0x4004d1 : movl $0x0,-0x4(%rbp) +record btrace bts +target record-btrace +si 4 0x00000000004004f6 40 for (i =3D 0, j =3D 0; i < 100; ++i) 1: x/i $pc =3D> 0x4004f6 : jle 0x4004e1 +record instruction-history 1 0x00000000004004d1 : movl $0x0,-0x4(%rbp) 2 0x00000000004004d8 : movl $0x0,-0x8(%rbp) 3 0x00000000004004df : jmp 0x4004f2 4 0x00000000004004f2 : cmpl $0x63,-0x4(%rbp) ... That looks reasonable. With taskset -c 4, however: ... $ taskset -c 4 ./gdb.sh -q -batch ./outputs/gdb.python/py-record-btrace/py-record-btrace -ex "set trace-comma= nds on" -ex "display /i \$pc" -ex "start" -ex "record btrace bts" -ex "si 4" -= ex "record instruction-history"=20 +display /i $pc +start Temporary breakpoint 1 at 0x4004d1: file /data/vries/gdb/src/gdb/testsuite/gdb.python/py-record-btrace.c, line 40. Temporary breakpoint 1, main () at /data/vries/gdb/src/gdb/testsuite/gdb.python/py-record-btrace.c:40 40 for (i =3D 0, j =3D 0; i < 100; ++i) 1: x/i $pc =3D> 0x4004d1 : movl $0x0,-0x4(%rbp) +record btrace bts +target record-btrace +si 4 0x00000000004004f6 40 for (i =3D 0, j =3D 0; i < 100; ++i) 1: x/i $pc =3D> 0x4004f6 : jle 0x4004e1 +record instruction-history 1 0x00000000004004d1 : movl $0x0,-0x4(%rbp) 2 0x00000000004004d8 : movl $0x0,-0x8(%rbp) 3 0x00000000004004df : jmp 0x4004f2 4 0x00000000004004e1 : mov -0x8(%rbp),%eax 5 0x00000000004004e4 : mov %eax,%edi 6 0x00000000004004e6 : call 0x4004a7 7 0x00000000004004eb : mov %eax,-0x8(%rbp) 8 0x00000000004004ee : addl $0x1,-0x4(%rbp) 9 0x00000000004004f2 : cmpl $0x63,-0x4(%rbp) ... That makes no sense as instruction history, this is just disassembly. --=20 You are receiving this mail because: You are on the CC list for the bug.=