From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 351ED3858D35; Tue,  7 Feb 2023 12:05:08 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 351ED3858D35
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1675771508;
	bh=SwcOmc7kFWLP+BrPWJnHCEvsYkqlNaRPmo8I6cMmEWE=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=mEnCBoDmvpqv4FIwS0ljegvXldpmddErA8t6pifsh4cxwFmIi8spDpMlVKywRByeN
	 s/2+tG2CzQXBDB5XKhhrZ0R0ZiLMp0FcljcgqH+Kg9udD9a/WyW4jH3+g25q3Mlv1j
	 bMQjFeNi6E0cPBf2C+Mk+wOZOtm85E79mm4UIljA=
From: "markus.t.metzger at intel dot com"
 <sourceware-bugzilla@sourceware.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: Tue, 07 Feb 2023 12:05:08 +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: markus.t.metzger at intel dot com
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: <bug-30075-4717-kodf8KUgDd@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-30075-4717@http.sourceware.org/bugzilla/>
References: <bug-30075-4717@http.sourceware.org/bugzilla/>
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: <gdb-prs.sourceware.org>

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

--- Comment #5 from Markus Metzger <markus.t.metzger at intel dot com> ---
The 'compressed return without call' error indicates a mismatch between the
trace and the binary.  A return is an indirect branch from the point of vie=
w of
the processor, but if we recorded a direct call right before the address we=
're
returning to, we can still compress this in the trace, and have the decoder
keep track of the call stack.

To debug such trace decode errors, it helps to print the output of `maint
btrace packet-history`.  We need the full history, so something like `maint
btrace packet-history 0, 1000`.

I will try to reproduce the errors.

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