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 F033B3858CDB; Tue, 24 Jan 2023 11:46:48 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org F033B3858CDB
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1674560808;
	bh=+7CCT2/NXyPV0pGF6rH1H7WcEkjz2PyMpTN2qfxgvLE=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=ePS3meVgPWCA03vxjwnanMk4Awiv1iLPGOAnNsv2lx5nD32qjaGZqgKSdWxLTvat3
	 zFkn1th37RwPKDcT2eLIT1L30EoHbYFQe4nw+BoEOGYM8R5waUJHtU09jHu5HIQcsv
	 In1NcvS4TLCC4fQG21udzOcyK7EgMw4eQFq8klNY=
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/30021] [gdb/tdep, powerpc64le] previous frame inner to
 this frame (corrupt stack?)
Date: Tue, 24 Jan 2023 11:46:48 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: tdep
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: <bug-30021-4717-abz08LQPod@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-30021-4717@http.sourceware.org/bugzilla/>
References: <bug-30021-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=3D30021

--- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #5)
> Created attachment 14611 [details]
> Tentative untested patch
>=20
> A hopefully more robust approach: detect stack restores in the epilogue a=
nd
> save the corresponding values in the epilogue cache.

Only changes in full test run:
...
-FAIL: gdb.base/unwind-on-each-insn.exp: instruction 5: $fba_value =3D=3D $=
main_fba
-FAIL: gdb.base/unwind-on-each-insn.exp: instruction 5: [string equal $fid
$main_fid]
+PASS: gdb.base/unwind-on-each-insn.exp: instruction 5: $fba_value =3D=3D $=
main_fba
+PASS: gdb.base/unwind-on-each-insn.exp: instruction 5: [string equal $fid
$main_fid]
...

Well, that's not bad.

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