Scarfski/tracy
1
0
Fork 0
mirror of https://github.com/wolfpld/tracy.git synced 2026-08-11 07:39:46 +00:00
Code Issues Packages Projects Releases Wiki Activity

Regenerate markdown manual.

Browse Source
This commit is contained in:
Bartosz Taudul
2026-08-06 22:37:24 +02:00
parent 6bca1141fe
commit 18eaa221d3
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
manual/tracy.md
View File

@@ -11,7 +11,7 @@ The user manual
**Bartosz Taudul** [\<wolf@nereid.pl\>](mailto:wolf@nereid.pl)
2026-07-28 <https://github.com/wolfpld/tracy>
2026-08-06 <https://github.com/wolfpld/tracy>
# Quick overview {#quick-overview .unnumbered}
@@ -2045,7 +2045,7 @@ Unlike C++, there's no automatic destruction mechanism in C, so you will need to
[^55]: GCC and Clang provide `__attribute__((cleanup))` which can used to run a function when a variable goes out of scope.
Zone text and name may be set by using the `TracyCZoneText(ctx, txt, size)`, `TracyCZoneValue(ctx, value)` and `TracyCZoneName(ctx, txt, size)` macros. Make sure you are following the zone stack rules, as described in section [3.4.2](#multizone)!
Zone text and name may be set by using the `TracyCZoneText(ctx, txt, size)`, `TracyCZoneValue(ctx, value)` and `TracyCZoneName(ctx, txt, size)` macros. For printf-style formatting, use the `TracyCZoneTextF(ctx, fmt, ...)` and `TracyCZoneNameF(ctx, fmt, ...)` variants, which accept a format string and arguments instead of a fixed-length text buffer. Make sure you are following the zone stack rules, as described in section [3.4.2](#multizone)!
#### Zone context data structure {#zonectx}