[Bug record/22725] "run" seems to reset btrace recording

[Bug record/22725] "run" seems to reset btrace recording

[blarsen at redhat dot com]

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.