Created attachment 1169895 [details] Object file to simplify testing Description of problem: Running 'pdwtags --verbose file.o' provides no output. Well it outputs one problem and quits. End returns 0. When trying upstream it outputs more similar problems on stderr, but it does not lack the output to stdout. Very similar to Bug 772358. Version-Release number of selected component (if applicable): dwarves-1.10-9.fc24.x86_64 How reproducible: 100% Steps to Reproduce: 1. pdwtags --verbose testfile.o | wc -l Actual results: die__process_unit: DW_TAG_restrict_type (0x37) @ <0x1a6> not handled! 0 Expected results: Positive number. But basically without 'wc' it should do some output. I've got 1096 when testing with latest upstream. Additional info: First commit that I can compile (943a0de0679a) outputs some errors on stderr, but I still get 998 lines of stdout. Those stopped appearing with 658a238b9890 of course, and it would be nice to have the latest upstream in. However the totally minimal thing we need to be able to run our checks is the following commit. If nothing else can be done then please at least back-port this one. commit be7b691756ff334705eb6faf51a196540e02e96c Author: Arnaldo Carvalho de Melo <acme> Date: Thu Aug 16 14:55:14 2012 -0300 dwarf_loader: Don't stop processing after finding unsupported tag
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle. Changing version to '25'.
dwarves-1.10-10.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-03a9404ecb
dwarves-1.10-10.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-03a9404ecb
dwarves-1.10-10.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.