Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@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:35:00 -0000	[thread overview]
Message-ID: <vt2u1awsplu.fsf@zenia.home> (raw)
In-Reply-To: <m3ptlllzp9.fsf@redhat.com>


Nick Clifton <nickc@redhat.com> writes:
>   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.
> 
>   My theory is that the only benefit gained by being able to ship a
>   stripped debuginfo file as opposed to an unstripped one is that it
>   reduces the shipping size, making a distribution smaller.  I am
>   assuming that hard disk space is not really an issue, just the size
>   of the shipped binaries.

I think the idea is to omit the debug info files altogether from the
distribution.  It'll make the debug info packages take longer to
download, but it's not a show-stopper, I think.


  reply	other threads:[~2003-06-11 13:35 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 [this message]
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
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=vt2u1awsplu.fsf@zenia.home \
    --to=jimb@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