[Fedora-packaging] Re: Importance of debuginfo packages
Tom 'spot' Callaway
tcallawa at redhat.com
Mon Aug 21 17:20:06 UTC 2006
On Mon, 2006-08-21 at 19:16 +0200, Axel Thimm wrote:
> On Mon, Aug 21, 2006 at 11:54:22AM -0500, Jason L Tibbitts III wrote:
> > >>>>> "JK" == Jesse Keating <jkeating at redhat.com> writes:
> > JK> Enough so that running gdb (gnu debugger) on the application will
> > JK> produce a meaningful traceback.
> > So what needs to be there in order for that to work?
> > I need to be able to superficially inspect a debuginfo package and
> > know whether it has enough stuff in it or not.
> That's very difficult, especially in projects with subdirectories that
> may redefine CFLAGS/CXXFLAGS w/o the builder noticing. sope/ogo is one
> nasty candidate for example.
> There are some safety pins in debuginfo, IIRC if it's turned on, but
> the debuginfo turns out empty the build will fail. That's how it gets
> my attention to fix debugging symbols at least :)
Indeed, debuginfo being empty is about the only giant red warning flag
that I'm aware of. :)
Tom "spot" Callaway: Red Hat Technical Team Lead || GPG ID: 93054260
Fedora Extras Steering Committee Member (RPM Standards and Practices)
Aurora Linux Project Leader: http://auroralinux.org
Lemurs, llamas, and sparcs, oh my!
More information about the packaging