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

["tromey at sourceware dot org" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=22725

            Bug ID: 22725
           Summary: "run" seems to reset btrace recording
           Product: gdb
           Version: unknown
            Status: NEW
          Severity: normal
          Priority: P2
         Component: record
          Assignee: unassigned at sourceware dot org
          Reporter: tromey at sourceware dot org
  Target Milestone: ---

I wanted to try btrace recording to debug an issue I was having, so I tried:

(gdb) record btrace
(gdb) r
The program being debugged has been started already.
Start it from the beginning? (y or n) y
[...]

Then when it stopped at my breakpoint I tried to reverse:

(gdb) set exec-direction reverse
Target does not support this operation.
(gdb) reverse-step
Target multi-thread does not support this command.

Hmmm....  (and as an aside note that one message mentions the
target while the other does not)

At this point I thought that maybe the issue was that I didn't specify
a recording method, so I tried again with "record btrace pt".

This too did not work.

What did work was to use "start", and only then "record btrace pt".

I think "run" should not interfere with btrace recording.
And, if forgetting the "pt" is an error (I don't know), then gdb
ought to mention it rather than making it seem like the command
did something useful.

-- 
You are receiving this mail because:
You are on the CC list for the bug.