Hi, On 8/21/06, Tom 'spot' Callaway <tcallawa@xxxxxxxxxx> wrote:
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@xxxxxxxxxx> 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. :)
May i know if debuginfo packages are really good in terms of let the end user debug applications to check if he is facing any crashes then why not we have separate debuginfo directory also present publicly for download? Regards, Parag. -- Fedora-packaging mailing list Fedora-packaging@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-packaging
