public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Allan Gottlieb <gottlieb@nyu.edu>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] what is /usr/lib64/debug ?
Date: Thu, 18 Aug 2011 10:27:37 -0400	[thread overview]
Message-ID: <yu939gyyeue.fsf@nyu.edu> (raw)
In-Reply-To: <CAJnEOsg88RYOgxdhmFueGHAV9_RZX8m9fMj20f4_wE7+1gsTzg@mail.gmail.com> (Daniel Pielmeier's message of "Thu, 18 Aug 2011 16:09:22 +0200")

On Thu, Aug 18 2011, Daniel Pielmeier wrote:

> 2011/8/18 Allan Gottlieb <gottlieb@nyu.edu>:
>> /usr/lib64/debug seems to have in it a duplicate (at least as far as
>> directory names are concerned) of much of /usr/lib64.
>>
>> For example
>>
>>    ajglap lib64 # /bin/pwd
>>    /usr/lib64/debug/usr/lib64
>>    ajglap lib64 # du -s * | sort -n | tail -10
>>    34020       mesa
>>    53148       gstreamer-0.10
>>    155992      icedtea6
>>    161360      llvm
>>    208932      qt4
>>    304016      xulrunner-devel-2.0
>>    308880      xulrunner-2.0
>>    618408      firefox
>>    669000      libwebkitgtk-1.0.so.0.7.2.debug
>>    1087848     libreoffice
>>    ajglap lib64 #
>>
>> Is this correct?  My system is ~amd64
>
>
> Do you have the splitdebug [1] FEATURE enabled?
>
> [1] http://www.gentoo.org/proj/en/qa/backtraces.xml

Bingo.

If I drop this feature (I turned it on for tracking a bug) will the
/usr/lib64/debug tree go away or must I delete it manually.

Also are there any other large subtrees I need to purge?

thanks for the help.
allan



  reply	other threads:[~2011-08-18 14:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-18 13:52 [gentoo-user] what is /usr/lib64/debug ? Allan Gottlieb
2011-08-18 14:09 ` Daniel Pielmeier
2011-08-18 14:27   ` Allan Gottlieb [this message]
2011-08-18 16:47     ` Allan Gottlieb

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=yu939gyyeue.fsf@nyu.edu \
    --to=gottlieb@nyu.edu \
    --cc=gentoo-user@lists.gentoo.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