3 ms·
Postmortem debugging on production builds and without debug info is just harder (depends on how much postmortem info your bug report system provides, and at lea
by flohofwoe 3y ago
Postmortem debugging on production builds and without debug info is just harder (depends on how much postmortem info your bug report system provides, and at least on Windows it still makes sense to create a PDB file and archive that inhouse to associate that with the minidump you're
getting from the bug report, slightly mismatched debug info is still much better than no debug info at all). A production build crash doesn't mean that the symptoms are not reproducible on a debug build, and investigating the debug build after the bug has been reproduced is a lot more convenient.
Also a lot more bugs show up and are already fixed during development and never even make it to CI or even out into the wild. That's were debug builds and debuggers are most useful (during the initial development phase).
Sometimes I really have a feeling that software development is moving backward in time (shakes head). Debuggers are incredibly poweful tools, use them!
- mgaunard 3y agoOf course you use the debugger to debug the core. Doesn't change the fact it's completely unrealistic to expect that you can do that with a full debug build. The industry has moved towards software as a service, and sometimes your service crashes and you need to figure out why. Even if you want to turn the problem into a regression test that you can run a debug build against, you'll still need to look at the core of the optimized build to figure out what happened to begin with.