TRACY-IMPORT-FUCHSIA(1)
β¨ tracy-import-fuchsia β¨
okay bestie, welcome to the tracy-import-fuchsia manual page π (that's the User Manual one, in case you were wondering which flavor of documentation you just wandered into) π«Ά
πΈ NAME πΈ
tracy-import-fuchsia β it's giving import Fuchsia's traces into Tracy π
π SYNOPSIS π
tracy-import-fuchsia input.fxt output.tracy
that's it. two files. in and out. iconic. π
β¨ DESCRIPTION β¨
okay so first things first: Tracy can import traces that were compressed with the Zstandard algorithm β like, say, if you ran them through the zstd command-line utility π¦. and here's the lil rule: any trace ending in the .zst extension? Tracy just assumes it's compressed. no cap, that's the vibe check. π«
now, the tea β: the Chrome tracing format doesn't document any way to provide source location data. none. zero. nothing. π BUT β and this is the slay part β the import-chrome and import-fuchsia utilities will recognize a custom loc tag in the root of zone begin events πβ¨. and you should be formatting that data in the usual filename:line style, like for example:
hello.c:42
and listen β providing the line number (including that colon, yes the colon matters bestie) is optional but highly recommended π₯. do it. trust.
if you want more info about the fuchsia trace format, go peek at https://fuchsia.dev/fuchsia-src/reference/tracing/trace-format π
π LIMITATIONS π
okay we gotta be real for a sec, no sugarcoating π:
- Tracy is a single-process profiler. so if the imported trace happens to contain PID entries, then each PID+TID pair will create a brand new pseudo-TID number, which the profiler will then decode into a PID+TID pair in thread labels π§΅. so likeβ¦ if you want to preserve the original TID numbers, your traces should just omit PID entries entirely. periodt. π
- the imported data may be severely limited π β either because it doesn't map directly onto the data structures Tracy uses, or because it's following undocumented practices. soβ¦ yeah. manage your expectations, bestie π«Ά.
π AUTHORS π
maintained by Bartosz Taudul <wolf@nereid.pl> π β and for more info about the upstream project, see https://github.com/wolfpld/tracy/ β
this man page is written for the Debian GNU/Linux system by Alan M Varghese <alan@digistorm.in> π
aaaand that's the whole page, bestie π it lives under tracy-import-fuchsia(1) in the tracy-import-fuchsia User Manual β go import some traces, you got this πβ¨π¦
π¦ where this page comes from
- ubuntu questing: tracy-import-fuchsia 0.11.0+ds-1build1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms