11 ms·
I think google of all companies could build a good autostripper reducing binaries by adding partial load assembly on misses. It cant be much slower then shovell
by darubedarob 9mo ago
I think google of all companies could build a good autostripper reducing binaries by adding partial load assembly on misses. It cant be much slower then shovelling a full monorepo assembly plus symbols into ram.
- loeg 9mo agoThe low-hanging fruit is just not shipping the debuginfo, of course.
- usefulcat 9mo agoIs compressed debug info a thing? It seems likely to compress well, and if it's rarely used then it might be a worthwhile thing to do?
- Gibbon1 9mo agoSmall brained primate comment. With embedded firmware you only flash the .text and and flash to the device. But you still can debug using the .elf file. In my case if I get a bus fault I'll pull the offending address off the stack and use bintools and the .elf to show me who was naughty. I think if you have a crash dump you should be able to make sense of things as long as you keep the unstripped .elf file around.
- loeg 9mo agoIt is: https://maskray.me/blog/2022-01-23-compressed-debug-sections https://maskray.me/blog/2022-01-23-compressed-debug-sections But the compression ratio isn't magical (approx. 1:0.25, for both zlib and zstd in the examples given). You'd probably still want to set aside debuginfo in separate files.