4 ms·

I've hit the same thing in Rust, probably for the same reasons. Isn't the simple solution to use detached debug files? I think Windows and Linux both support

I've hit the same thing in Rust, probably for the same reasons. Isn't the simple solution to use detached debug files? I think Windows and Linux both support them. That's how phones like Android and iOS get useful crash reports out of small binaries, they just upload the stack trace and some service like Sentry translates that back into source line numbers. (It's easy to do manually too) I'm surprised the author didn't mention it first. A 25 GB exe might be 1 GB of code and 24 GB of debug crud.

dwattttt 10mo ago
> I think Windows and Linux both support them. Detached debug files has been the default (only?) option in MS's compiler since at least the 90s. I'm not sure at what point it became hip to do that around Linux.
- kvemkon 10mo ago
  Since at least October 2003 on Debian: [1] "debhelper: support for split debugging symbols" https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=215670 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=215670 [2] https://salsa.debian.org/debian/debhelper/-/commit/79411de849c878b56c269b88a49c6b1ce15310d0 https://salsa.debian.org/debian/debhelper/-/commit/79411de84...
nicoburns 10mo ago
> Isn't the simple solution to use detached debug files? It should be. But the tooling for this kind of thing (anything to do with executable formats including debug info and also things like linking and cross-compilation) is generally pretty bad.