Unstripped binary system 2018
The primary benefit, for the vast majority of cases, is just to save disk space. A secondary, unstripped binary system 2018 much more dubious benefit, is that it also makes the binary more difficult to disassemble or reverse engineer.
It may also reduce the memory footprint a little, unstripped binary system 2018 in many cases it'll be a negligible savings. The biggest detriment is that it makes debugging significantly more difficult if you run into a problem. It's really about debugging, "cleanliness", and personal preferences. Some people prefer to always used stripped binaries for production or "shipped" software.
Some people prefer to always leave the symbols included, "just in case". Personally, I prefer to have symbols included. I've had a couple of really frustrating situations over the year where a commercial application was segfaulting or otherwise crashing and I had no ability to pinpoint where the problem was, because the binaries were stripped. In at least a few of those cases, the vendor ended up sending me a non-stripped version to run with, until it crashed again, so we could get more useful debugging information.
I'm just wondering if stripping a program file has more benefits than just saving disk space. On embedded systems where storage is tight it will save some disk space.
Unstripped binary system 2018 a wee bit on memory. Christopher Cashell 7, 1 25 I have likewise attached unstripped binary system 2018 to a dying or dead process and would have been up a creek had it not been for the unstripped symbols.
My take is that stripping symbols is only for memory conservation and better cache-line usage. But test the latter unstripped binary system 2018 optimization may ignore your expectations. You make an excellent point. Marcin 1, 1 11 Brad Clawsie 2 7.