Re: git binary size...

From: H. Peter Anvin <hpa@zytor.com>
Date: Jan 11, 2006, 19:58 UTC
Message-ID: <43C5636D.505@zytor.com>
In-Reply-To: <Pine.LNX.4.64.0601111134560.5073@g5.osdl.org>

Linus Torvalds wrote:

Show 10 quoted lines

> 
> Well, that ends up shaving some more from the binaries, but at a much 
> bigger cost than just removing "-g".
> 
> With stripped binaries, you can't really do _anything_. You get a 
> core-file, and you're screwed. 
> 
> With non-stripped binaries you can at least see the function the SIGSEGV 
> happened in, and you usually even get a half-way decent backtrace etc.
>

That's the really nice bit with the way e.g. RPM does it. You don't have to have the debug information around most of the time, but you can do "yum install git-debuginfo" and suddenly you have it all -- and yet the binary is unchanged, so your random core file actually matches the debuginfo.

	-hpa