From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id AB3173858415; Fri, 5 Apr 2024 11:31:05 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AB3173858415 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1712316665; bh=8DRXx13bKkqoabiiXLeQigGn6sNweFI5s12f3X6L/h0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=KRymvuhu5DP+2+WDLCZBX0c4xJEex4kXIcWwKFcoVOIHMej+vrSx250+piKjkhIss vcHQeURCcUo2RRUylJvUhONrZ9aL8Ds2gvuY+bEcBFfX0ZfHAvpHn4maaDbB0RdjDc ZdmD/V2Bd8QIena8haFw/X7HYd+g3sk+Qb1kDvmY= From: "brandon.belew at zetier dot com" To: gdb-prs@sourceware.org Subject: [Bug record/18059] Why can't "record instruction-history" and "record function-call-history" work with "record full"? Date: Fri, 05 Apr 2024 11:31:05 +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: brandon.belew at zetier 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: cc 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=3D18059 Brandon Belew changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |brandon.belew at zetier do= t com --- Comment #3 from Brandon Belew --- Bumping this issue. I guess this should really be more of a feature request than a bug, but from a "record full" recording, surely there would be enough information to figure out which functions were called? There *definitely* should be enough information to list the instruction history, we've already recorded every instruction.=20 "record full" is available on substantially more targets than "record btrac= e" and the "record function-call-history" command would be very useful. --=20 You are receiving this mail because: You are on the CC list for the bug.=