From: Michael Snyder <msnyder@redhat.com>
To: Nick Clifton <nickc@redhat.com>
Cc: gdb-patches@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: RFC: strip --strip-nondebug
Date: Thu, 05 Jun 2003 18:29:00 -0000 [thread overview]
Message-ID: <3EDF8C1C.5D5067DE@redhat.com> (raw)
In-Reply-To: <m34r34a590.fsf@redhat.com>
Nick Clifton wrote:
>
> Hi Guys,
>
> I am seeking comments and criticisms on the attached patch. It adds
> a new switch to strip:
>
> --strip-nondebug
>
> This can be used to create an output file which only contains the
> debug information from an executable. This would allow stripped
> binaries to be shipped with separate debug info files, and provided
> that the debugger supported it, they could still be debugged.
>
> The patch is incomplete - it needs a ChangeLog entry as well as
> modifications to NEWS and binutils.texi to document the new
> functionality, but I will write all of these once/if the patch is
> in acceptable state.
How big a reduction in size would you expect, typically?
I'm a little ignorant, but what strippable info is in there
that gdb doesn't need?
next prev parent reply other threads:[~2003-06-05 18:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 15:57 Nick Clifton
2003-06-05 16:06 ` Ian Lance Taylor
2003-06-05 16:24 ` Daniel Jacobowitz
2003-06-05 16:14 ` Andrew Cagney
2003-06-05 16:24 ` Elena Zannoni
2003-06-05 17:08 ` Nick Clifton
2003-06-05 19:19 ` Elena Zannoni
2003-06-06 11:17 ` Nick Clifton
2003-06-06 13:11 ` Elena Zannoni
2003-06-06 14:32 ` Nick Clifton
2003-06-06 14:51 ` Nick Clifton
2003-06-06 21:34 ` Andrew Cagney
2003-06-07 10:39 ` Nick Clifton
2003-06-07 15:37 ` Andrew Cagney
2003-06-05 18:29 ` Michael Snyder [this message]
2003-06-05 18:48 ` Daniel Jacobowitz
2003-06-05 19:06 ` Michael Snyder
2003-06-05 19:13 ` Elena Zannoni
2003-06-05 19:47 ` Nick Clifton
2003-06-05 19:54 ` Kris Warkentin
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=3EDF8C1C.5D5067DE@redhat.com \
--to=msnyder@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=nickc@redhat.com \
/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