Previous: Tracepoint Variables, Up: Tracepoints [Contents][Index]
In some situations, the target running a trace experiment may no
longer be available; perhaps it crashed, or the hardware was needed
for a different activity. To handle these cases, you can arrange to
dump the trace data into a file, and later use that file as a source
of trace data, via the target tfile
command.
tsave [ -r ] filename
Save the trace data to filename. By default, this command
assumes that filename refers to the host filesystem, so if
necessary GDB will copy raw trace data up from the target and
then save it. If the target supports it, you can also supply the
optional argument -r
(“remote”) to direct the target to save
the data directly into filename in its own filesystem, which may be
more efficient if the trace buffer is very large. (Note, however, that
target tfile
can only read from files accessible to the host.)
target tfile filename
Use the file named filename as a source of trace data. Commands
that examine data work as they do with a live target, but it is not
possible to run any new trace experiments. tstatus
will report
the state of the trace run at the moment the data was saved, as well
as the current trace frame you are examining. filename must be
on a filesystem accessible to the host.