Re:How to build highly-debuggable C++ binaries
by pjc50 on Tuesday July 30, 2024 @04:38AM
(#41107206)
I had to do that when dealing with a device that was only debuggable over USB. When it crashed, that also took out the uplink and the debugger. So I had to record the stack trace in an area of memory specified as uninitialized, then dump it out as one of the first things to happen after a reboot.
[ Parent
| on HN ]
There are no comments on this comment yet.