Summary: | USE="debug" vs. FEATURES="nostrip splitdebug" | ||
---|---|---|---|
Product: | Documentation | Reporter: | Marian Kyral <mkyral> |
Component: | Project-specific documentation | Assignee: | Gentoo Quality Assurance Team <qa> |
Status: | RESOLVED WORKSFORME | ||
Severity: | enhancement | CC: | flameeyes |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Marian Kyral
2008-12-11 08:14:16 UTC
USE=debug is not supposed to be used by most users, since it enables debug codepaths that usually can lead to: - slower code; - code that aborts on mistakes instead of handling them "nicely"; (assertions) - code that produces debug output (in the case of nano, making the editor mostly useless); So the meaning of the two have to stay separated. As for "nostrip splitdebug", the latter is enough, so it's just FEATURES=splitdebug, and at that point it's simpler to just enable it system-wide. On a system with 1369 packages, my /usr/lib/debug is just shy of 5GB, but this is also having -ggdb enabled for all of them. Aha: $ euse -I debug [- ] debug - Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see http://www.gentoo.org/proj/en/qa/backtraces.xml Problem is that I never before have an idea to check what the debug USE flag really means :-( I don't want to enable the splitdebug FEATURE globally - I have only 6GB in /usr free on my laptop now. Bud in another issue with Amarok2, mysql and -fPIC flag is a solution how to set some environment variables locally with newest portage. # cat /etc/portage/env/kde-base/kate FEATURES="${FEATURES} splitdebug" CFLAGS="${CFLAGS} -ggdb" CXXFLAGS="${CFLAGS}" I've created such file for all important packages (qt-, kdelibs, kate...) and now I'm recompiling these packages. After recompiling of all qt- packages, the debug directory has 480MB. Will see the kdelibs result. Maybe should be this solution also included in the documentation. Don't see anything for QA to do here... |