public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "brandon.belew at zetier dot com" <sourceware-bugzilla@sourceware.org>
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 [thread overview]
Message-ID: <bug-18059-4717-kjeWmS219b@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18059-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18059
Brandon Belew <brandon.belew at zetier dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |brandon.belew at zetier dot com
--- Comment #3 from Brandon Belew <brandon.belew at zetier dot com> ---
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.
"record full" is available on substantially more targets than "record btrace"
and the "record function-call-history" command would be very useful.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-04-05 11:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 23:24 [Bug gdb/18059] New: " dje at google dot com
2015-02-28 0:18 ` [Bug record/18059] " dje at google dot com
2015-02-28 0:22 ` palves at redhat dot com
2015-02-28 15:23 ` dje at google dot com
2024-04-05 11:31 ` brandon.belew at zetier dot com [this message]
2024-07-10 17:40 ` blarsen at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-18059-4717-kjeWmS219b@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).