Description of problem:
libvirt uses pdwtags as part of 'make check' to ensure binary compatible layouts between versions. However, on rawhide, this check fails (see bug 613600), since gcc is new enough to be outputting additional DWARF debugging elements that pdwtags has not yet learned to parse.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. I've gone ahead and pre-compiled the same file on both F16 (gcc-4.6.2-1.fc16.x86_64 and binutils-126.96.36.199.1-6.fc16.x86_64) and rawhide (versions shown above), and attached the two object files (the compiled file is libvirt_net_rpc_la-virkeepaliveprotocol.o from libvirt.git); the steps below use the same version of pdwtags, so the only difference is in the gcc and binutils versions used to make the .o file
2. pdwtags --verbose f16.o | wc
3. pdwtags --verbose f17.o
2. 280 1006 5310
3. die__process_function: DW_TAG_INVALID (0x4109) @ <0x58c> not handled!
Both .o files should be decoded, with only minor variations in output according to whatever minor variations were present in the gcc code generation.
I also reproduced this on the i686 versions of the packages.
Created attachment 551301 [details]
compiled on F16
Created attachment 551307 [details]
compiled on F17
Fedora Bugzappers volunteer triage team
dwarves-1.10-1.fc17 has been submitted as an update for Fedora 17.
dwarves-1.10-1.fc16 has been submitted as an update for Fedora 16.
dwarves-1.10-1.fc15 has been submitted as an update for Fedora 15.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dwarves-1.10-1.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
dwarves-1.10-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
dwarves-1.10-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.