public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "blarsen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug record/22725] "run" seems to reset btrace recording
Date: Fri, 12 Jan 2024 10:12:17 +0000 [thread overview]
Message-ID: <bug-22725-4717-P9g9t5LcGf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22725-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22725
Guinevere Larsen <blarsen at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |blarsen at redhat dot com
--- Comment #1 from Guinevere Larsen <blarsen at redhat dot com> ---
I still see this issue on current GDB, so this is still a valid bug
Adding "pt" at the end of "record btrace" is not required, that is completely
unrelated to your issue. Also, btrace is incidental, this issue also occurs
with record full.
I think the problem is that when you "run" or "start" the inferior, the target
stack gets re-set and there is nothing in GDB that checks if there was a record
target that should be added again.
A related problem is that the target has to have started running before we can
start recording. It would be nice if you could set a target to record before
even running.
The issue with solving this comes from the question: when should the recording
target be added? once we enter main? Once we enter __libc_start_main? I would
argue that most users would want the former, but that is a decision that needs
to be made, and properly handled in the run and start codes.
--
You are receiving this mail because:
You are on the CC list for the bug.
parent reply other threads:[~2024-01-12 10:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-22725-4717@http.sourceware.org/bugzilla/>]
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-22725-4717-P9g9t5LcGf@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).