From: Jakub Jelinek <jakub@redhat.com>
To: Nick Clifton <nickc@redhat.com>
Cc: gdb-patches@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: RFC: Support for separate debug info files
Date: Wed, 11 Jun 2003 13:45:00 -0000 [thread overview]
Message-ID: <20030611134532.GW24872@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <m3ptlllzp9.fsf@redhat.com>
On Wed, Jun 11, 2003 at 10:40:18AM +0100, Nick Clifton wrote:
> This leads me to my main point. Do we need the ability to create
> stripped debuginfo files ? The original patch did this, but it
> turns out to be problematical since the debuginfo files need to
> contain dummy versions of the .text, .data, etc sections. Doing
> this, rather than just stripping them out, looked non-trivial, so I
> decided to skip it for this version.
By stripped debuginfo files you mean what eu-strip -f creates, right?
(ie. ET_DYN resp. ET_EXEC with the sections which were not stripped
turned into SHT_NOBITS sections).
I think harddrive space is not the main problem (although the difference can
be big, openoffice-debuginfo ATM takes 1.2GB and when all the .text/.data
etc. sections were in as well, I think it could grow easily by further
300MB), which is how you install it, because suddenly you have to transfer
more bytes from the network in order to debug packages, and not everybody
has a fast pipe.
Jakub
next prev parent reply other threads:[~2003-06-11 13:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 9:43 Nick Clifton
2003-06-11 13:35 ` Jim Blandy
2003-06-11 13:43 ` Daniel Jacobowitz
2003-06-11 14:15 ` Nick Clifton
2003-06-11 19:28 ` Jim Blandy
2003-06-11 13:45 ` Jakub Jelinek [this message]
2003-06-11 14:27 ` Nick Clifton
2003-06-11 17:59 ` Elias Athanasopoulos
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=20030611134532.GW24872@sunsite.ms.mff.cuni.cz \
--to=jakub@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