I looked through the archives and couldn't see any threads that were relevant so here I go...Should some debugging symbols be left in the applications while they are in "test?" I just ran into a case wherein I would have to recompile quite a few things to get any kind of debugging output.
Was this done due to space constraints or something? Or are is this a Q/A requirement that we test packages as they will be delivered to the distribution? Could seperate versions with symbols be available in rawhide for this purpose?
Sean
On Sun, 3 Apr 2005, Sean Bruno wrote:
I looked through the archives and couldn't see any threads that were relevant so here I go...Should some debugging symbols be left in the applications while they are in "test?"
That's not necessary. You just need to install the corresponding -debuginfo packages from
http://download.fedora.redhat.com/pub/fedora/linux/core/development/$arch/de...
(substituting $arch with your architecture).
Both gdb and valgrind appear to automatically detect -debuginfo packages and use the debugging information therein, including the source code, so you shouldn't need to do anything special other than installing the -debuginfo packages.
Note that normally one -debuginfo package is generated per source RPM, not one per binary RPM. To find the source rpm name for a package, use
rpm -qi package
and look for "Source RPM".
On Sun, 2005-04-03 at 10:28 -0400, Robin Green wrote:
That's not necessary. You just need to install the corresponding -debuginfo packages from
http://download.fedora.redhat.com/pub/fedora/linux/core/development/$arch/de...
(substituting $arch with your architecture).
Both gdb and valgrind appear to automatically detect -debuginfo packages and use the debugging information therein, including the source code, so you shouldn't need to do anything special other than installing the -debuginfo packages.
Note that normally one -debuginfo package is generated per source RPM, not one per binary RPM. To find the source rpm name for a package, use
rpm -qi package
and look for "Source RPM".
-- Robin
Thank you very much for the insight. I was completely ignorant of this feature. Let's see if I can put this information to some kind of good use. A little knowledge can be dangerous u know!
Sean