| Debugging with GDB: Analyze Collected Data |
|---|
Next: Tracepoint Variables, Previous: Set Tracepoints, Up: Tracepoints [Contents][Index]
After the tracepoint experiment ends, you use GDB commands
for examining the trace data. The basic idea is that each tracepoint
collects a trace snapshot every time it is hit and another
snapshot every time it single-steps. All these snapshots are
consecutively numbered from zero and go into a buffer, and you can
examine them later. The way you examine them is to focus on a
specific trace snapshot. When the remote stub is focused on a trace
snapshot, it will respond to all GDB requests for memory and
registers by reading from the buffer which belongs to that snapshot,
rather than from real memory or registers of the program being
debugged. This means that all GDB commands
(print, info registers, backtrace, etc.) will
behave as if we were currently debugging the program state as it was
when the tracepoint occurred. Any requests for data that are not in
the buffer will fail.
| • tfind: | How to select a trace snapshot | |
| • tdump: | How to display all data for a snapshot | |
| • save tracepoints: | How to save tracepoints for a future run |