Bug 185227 - rpmlint uses objdump -T on .so.x.debug files -debuginfo, which fails
Summary: rpmlint uses objdump -T on .so.x.debug files -debuginfo, which fails
Alias: None
Product: Fedora
Classification: Fedora
Component: rpmlint
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Ville Skyttä
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2006-03-12 07:30 UTC by Hans de Goede
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2006-04-11 18:24:19 UTC

Attachments (Terms of Use)
Fix (1.05 KB, patch)
2006-03-12 10:01 UTC, Ville Skyttä
no flags Details | Diff

Description Hans de Goede 2006-03-12 07:30:41 UTC
Try running rpmlint on any -debuginfo rpm on a fully up2date rawhide, it gives:
[hans@shalem t]$ rpmlint
W: adime-debuginfo objdump-failed 

The probem is the use of the -T option which doesnot work on .so.x.debug, hre I
try to use it on another .so.x.debug file:
[hans@shalem t]$ LC_ALL=C objdump --headers --private-headers -T
/usr/lib/debug/usr/lib64/libgda-3.so.3.0.0.debug &> /dev/null; echo $?

Without -T:
[hans@shalem t]$ LC_ALL=C objdump --headers --private-headers
/usr/lib/debug/usr/lib64/libgda-3.so.3.0.0.debug &> /dev/null; echo $?

Please change romlint to not use the -T objdump option on .so.x.debug files.

Comment 1 Ville Skyttä 2006-03-12 10:01:19 UTC
Created attachment 126007 [details]

Upstream CVS now has the attached patch, it will be included in the next
package revision.

Comment 2 Ville Skyttä 2006-03-12 10:03:49 UTC
Oh, by the way, using objdump -T on a *.debug file extracted from an executable
instead of a library does not fail, but doesn't seem to print too useful info
either.  What do you think, should -T be dropped from the objdump arguments only
for *.debug extracted from *.so*, or left as is in the patch?

Comment 3 Hans de Goede 2006-03-12 10:05:18 UTC
I have no real opinion on this, just take the easy route and leave it as is.

Comment 4 Ville Skyttä 2006-04-11 18:24:19 UTC
Done in 0.76-1.

Note You need to log in before you can comment on or make changes to this bug.