From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: git binary size... Date: Wed, 11 Jan 2006 11:58:37 -0800 Message-ID: <43C5636D.505@zytor.com> References: <43C558FB.3030102@op5.se> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Andreas Ericsson , Junio C Hamano , Git Mailing List X-From: git-owner@vger.kernel.org Wed Jan 11 20:59:30 2006 Return-path: Envelope-to: gcvg-git@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by ciao.gmane.org with esmtp (Exim 4.43) id 1Ewm7h-0001jO-RQ for gcvg-git@gmane.org; Wed, 11 Jan 2006 20:59:10 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932483AbWAKT64 (ORCPT ); Wed, 11 Jan 2006 14:58:56 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932485AbWAKT64 (ORCPT ); Wed, 11 Jan 2006 14:58:56 -0500 Received: from terminus.zytor.com ([192.83.249.54]:44763 "EHLO terminus.zytor.com") by vger.kernel.org with ESMTP id S932484AbWAKT6z (ORCPT ); Wed, 11 Jan 2006 14:58:55 -0500 Received: from [10.4.1.13] (yardgnome.orionmulti.com [209.128.68.65]) (authenticated bits=0) by terminus.zytor.com (8.13.4/8.13.4) with ESMTP id k0BJwhwr003867 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Jan 2006 11:58:43 -0800 User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929) X-Accept-Language: en-us, en To: Linus Torvalds In-Reply-To: X-Virus-Scanned: ClamAV version 0.87.1, clamav-milter version 0.87 on localhost X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on terminus.zytor.com Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: Linus Torvalds wrote: > > 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