[Bug breakpoints/16508] New: "-trace-find frame-number" does not work if trace file was taken while trace was running

["marc.khouzam at ericsson dot com" <sourceware-bugzilla at sourceware dot org>]

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

            Bug ID: 16508
           Summary: "-trace-find frame-number" does not work if trace file
                    was taken while trace was running
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: breakpoints
          Assignee: unassigned at sourceware dot org
          Reporter: marc.khouzam at ericsson dot com

I notice that GDB allows to save a trace file while a trace experiment is
running.  This sounds like a nice thing as it can allow to look at the content
of the trace records without stopping the experiment (this would require a
second GDB instance, but that is fine).  One can even imagine an automatic
saving of the trace records periodically when using circular-buffer.

The problem is that when loading a trace file that was saved while the
experiment was running, the command "-trace-find frame-number" fails saying:

^error,msg="May not look at trace frames while trace is running."

However 'tfind' works in that case.  'tfind' seems to make a difference between
the case when the experiment is really running, and the one when we are looking
at a trace file saved with an experiment running.

It would be good to have '-trace-find work like 'tfind' in that case.

(gdb) tstatus
Using a trace file.
Trace is running on the target.
Collected 6944 trace frames.
Trace buffer has 1125088 bytes of 5242880 bytes free (78% full).
Trace will stop if GDB disconnects.
Not looking at any trace frame.
Trace started at 1390932822.561872 secs.

(gdb) tfind 0
Found trace frame 0, tracepoint 1
#0  doWork () at ../src/Producer.cpp:84
84              sleepCount++;

(gdb) interpreter-exec mi "-trace-find frame-number 0"
^error,msg="May not look at trace frames while trace is running."

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