Function Call Tracing

Function call tracing captures entry and exit points in C/C++ code to generate per-thread logs. Enable it by adding -finstrument-functions to your compiler flags, link against the instrumentation library, and run your program to produce trace logs that record every function invocation with timing data.

Yes. Convert your trace logs to Perfetto's Chrome JSON format using the included converter, then upload the JSON file to ui.perfetto.dev. Perfetto displays call graphs, thread timelines, and performance hotspots from your instrumented C/C++ application.

Instrument your build with function call tracing to capture per-thread execution logs, then convert them to Perfetto format. This approach isolates thread behavior, reveals contention points, and visualizes call stacks across your entire multi-threaded workload.

No source code changes are required. Function call tracing works through compiler instrumentation flags (-finstrument-functions) and linking the trace library. The compiler automatically inserts entry/exit hooks into every function during compilation.

Tracing generates per-thread log files (trace_<tid>.log) containing function entry/exit records with timestamps. These logs can be converted to Perfetto's JSON format for visualization or analyzed programmatically for performance metrics.

Yes. Integrate tracing by adding -finstrument-functions to CFLAGS and linking with -ltrace and -lpthread. The instrumentation library is designed as a drop-in component for standard C/C++ build workflows.