Writing my own trace decoder
Debugging our main cellular platform depended on the chip vendor’s closed trace tool. I wrote my own in C++20 and checked it against the vendor’s output at every step. On 108,755 traces, it produces the same bytes.
Debugging our main cellular platform depended on the chip vendor’s trace tool. It was closed, so when it had problems, nobody outside the vendor could fix them.
A replacement is only worth using if people trust it as much as the original. So the real job wasn’t just building it. It was proving that it reads traces exactly the way the vendor’s tool does.
What it does
I wrote it in C++20, with a Dear ImGui GUI and a command-line version. It handles capture, decoding, merging, pcap export, GSMTAP export for Wireshark, symbols and a Ctrl+K command palette. It idles at 1.9% CPU with a 2-million-row log open.
Checked against the vendor’s tool
Every stage is tested against the vendor tool’s own output, with golden tests covering 3.7 million records. Decoding is compared byte for byte. I also rewrote one of the vendor’s message decoders and checked it the same way: 37,340 of 37,340 messages match. Capture has nothing to compare against, so it got a soak test instead.
Crash analysis
The crash analyzer walks the RTOS task blocks and queues, and unwinds the stacks using DWARF CFI. Its call stacks are compared with the vendor’s crash report.
Conclusion
Decoding is byte-identical on 108,755 traces, and 8.7 MB decodes in 0.8 s. 57 of 57 crash call stacks match the vendor’s report. A 30-minute capture soak lost nothing on the PC side.
Matching the vendor’s tool proves that mine agrees with it, not that both are right. For a replacement, agreement is the point.