Bartosz Taudul
5563461201
The tool only reported "was executing" entry stacks, while the sample entry stacks window now defaults to showing the stacks through which a symbol was reached. The model was told there is no data for symbols which never executed directly, even when the window right next to it displayed their entry stacks. Add an optional "mode" parameter with the "reached" (non-reentrant), "reached_recursive" and "executing" values. The default matches the UI default. Inline symbols are now accepted, as the reached maps cover them directly, and the executing mode can use their exact statistics. The reported mode is included in the tool output, and the chat view shows it in the tool call label. The tool description keeps the mode summaries short. The detailed guidance on choosing a mode is in the optimization skill, so it only occupies context when the skill is loaded.
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