strace - Swiss Army Knife to Trace, Analyze, RT Debug
summary
strace proves itself as a daily Swiss Army knife by showing exact system calls, file paths and timing so you can find missing config files and which libraries get loaded, attach to running PIDs with -p, or trace forks and execs with -f and -ff to produce per‑process logs. use -s to dump long strings or -x for hex, and -ttt or -r to get absolute or relative microsecond timing. demos show a 1.7s blocking read and a 0.64s sensor interval and include replaying traces to reproduce timing patterns.
AI-written summary · about
chapters (15)
- 0:00strace introduction
- 1:02What is strace and docs
- 6:39strace and ptrace
- 9:06strace modes
- 11:15Tracing a simple command
- 15:53How strace captures calls
- 21:08Output and file descriptors
- 23:14Filtering system calls
- 27:28Saving output to files
- 30:38String sizes and verbosity
- 34:33Selecting system calls
- 36:59Timing options
- 39:28Embedded device sensors example
- 42:38Replaying traced processes
- 46:10Summary
related talks
37mUsing STRACE to troubleshoot issues
29mUsing strace to troubleshoot issues
46mThe Hidden Secrets of Debugging
48mDPTrace: Dual Purpose Trace for Exploitability Analysis of Program Crashes
42mWhat Really Happens When You Hit a Breakpoint
37mDebugging Without Borders
31mLiterate Tracing
53mDebugging: past, present and future