When libbacktrace has no debug info for a pc, CallstackDataCb names the frame from dladdr but keeps libbacktrace's lowaddr, which is 0 there, as its symbol address, and SymInfoCallback then overwrites it with libbacktrace's symval, also 0, since libbacktrace has no symbol for it either. Every such frame (on macOS, every frame in a system library) gets symbol address 0, so the sampling statistics count all of them as one symbol with no name. Record dli_saddr as the frame's symbol address, as the dladdr-only DecodeCallstackPtr (TRACY_HAS_CALLSTACK 5) does, and have SymInfoCallback keep the address CallstackDataCb found when libbacktrace reports no symbol. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Tracy Profiler
A real time, nanosecond resolution, remote telemetry, hybrid frame and sampling profiler for games and other applications.
Tracy supports profiling CPU (Direct support is provided for C, C++, Lua, Python and Fortran integration. At the same time, third-party bindings to many other languages exist on the internet, such as Rust, Zig, C#, OCaml, Odin, etc.), GPU (All major graphics/compute APIs: OpenGL, Vulkan, Direct3D 11/12, Metal, OpenCL, CUDA, WebGPU.), memory allocations, locks, context switches, automatically attribute screenshots to captured frames, and much more.
- Documentation for usage and build process instructions
- Releases containing the documentation (
tracy.pdf) and compiled Windows x64 binaries (Tracy-<version>.7z) as assets - Changelog
- Interactive demo
An Introduction to Tracy Profiler in C++ - Marcos Slomp - CppCon 2023
Introduction to Tracy Profiler v0.2
New features in Tracy Profiler v0.3
New features in Tracy Profiler v0.4
New features in Tracy Profiler v0.5
New features in Tracy Profiler v0.6
New features in Tracy Profiler v0.7
New features in Tracy Profiler v0.8


