git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Coywolf Qi Hunt <coywolf@gmail.com>
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: Thu, 12 Jan 2006 10:12:38 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0601121011370.3535@g5.osdl.org> (raw)
In-Reply-To: <2cd57c900601120215pdb5da27l@mail.gmail.com>



On Thu, 12 Jan 2006, Coywolf Qi Hunt wrote:
> >
> > With stripped binaries, you can't really do _anything_. You get a
> > core-file, and you're screwed.
> 
> Are you sure?

I'm sure.

> In gdb:
> 
> No symbol table is loaded.  Use the "file" command.
> (gdb) bt
> #0  0xb7f16445 in ext2fs_mark_generic_bitmap () from /lib/libext2fs.so.2

Note where the debug info comes from. It comes from the _library_.

> So with stripped binary, I still get the backtrace to locate the buggy
> function.

No you don't. With the _non-stripped_ library you get the backtrace. 
There's no backtrace at all for the binary itself.

		Linus

      parent reply	other threads:[~2006-01-12 18:12 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
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 [this message]

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=Pine.LNX.4.64.0601121011370.3535@g5.osdl.org \
    --to=torvalds@osdl.org \
    --cc=ae@op5.se \
    --cc=coywolf@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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).