From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andreas Ericsson <ae@op5.se>, Junio C Hamano <junkio@cox.net>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: git binary size...
Date: Wed, 11 Jan 2006 11:58:37 -0800 [thread overview]
Message-ID: <43C5636D.505@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0601111134560.5073@g5.osdl.org>
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
next prev parent reply other threads:[~2006-01-11 19:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 18:26 git binary size Linus Torvalds
2006-01-11 19:14 ` Andreas Ericsson
2006-01-11 19:39 ` H. Peter Anvin
2006-01-11 19:54 ` Andreas Ericsson
2006-01-11 19:56 ` H. Peter Anvin
2006-01-11 20:00 ` Andreas Ericsson
2006-01-11 19:40 ` Junio C Hamano
2006-01-11 19:44 ` Linus Torvalds
2006-01-11 19:58 ` H. Peter Anvin [this message]
2006-01-12 10:15 ` Coywolf Qi Hunt
2006-01-12 13:49 ` Andreas Ericsson
2006-01-12 17:37 ` H. Peter Anvin
2006-01-12 18:13 ` Linus Torvalds
2006-01-12 18:32 ` Johannes Schindelin
2006-01-12 18:46 ` Linus Torvalds
2006-01-12 19:16 ` H. Peter Anvin
2006-01-20 18:00 ` Jon Loeliger
2006-01-12 18:12 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43C5636D.505@zytor.com \
--to=hpa@zytor.com \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).