public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/18059] New: Why can't "record instruction-history" and "record function-call-history" work with "record full"?
Date: Fri, 27 Feb 2015 23:24:00 -0000 [thread overview]
Message-ID: <bug-18059-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=18059
Bug ID: 18059
Summary: Why can't "record instruction-history" and "record
function-call-history" work with "record full"?
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: dje at google dot com
If I'm doing full recording, why can't I see the instruction history or
function call history?
Is there an error in my mental model of how this is supposed to work?
(gdb) record inst
You can't do that when your target is `record-full'
(gdb) record func
You can't do that when your target is `record-full'
(gdb)
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2015-02-27 23:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 23:24 dje at google dot com [this message]
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
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@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).