Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1722178 - gdb 8.3.50.20190610 prints "Missing separate debuginfos" on stderr, not stdout
Summary: gdb 8.3.50.20190610 prints "Missing separate debuginfos" on stderr, not stdout
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gdb
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Sergio Durigan Junior
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1721483
TreeView+ depends on / blocked
 
Reported: 2019-06-19 15:30 UTC by Petr Viktorin
Modified: 2019-06-21 19:26 UTC (History)
6 users (show)

Fixed In Version: gdb-8.3.50.20190610-17.fc31
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-21 19:26:43 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Petr Viktorin 2019-06-19 15:30:15 UTC 
In a recent gdb update,  "Missing separate debuginfos"  messages started appearing on stderr, rather than on stdout as in previous versions.

Fedora 30:

$ rpm -q gdb
gdb-8.3-3.fc30.x86_64
$ echo 'run' | gdb --args python3 > /dev/null
$

Fedora Rawhide:

$ rpm -q gdb
gdb-8.3.50.20190610-16.fc31.x86_64
$ echo 'run' | gdb --args python3 > /dev/null

warning: Unable to open "librpm.so.8" (librpm.so.8: cannot open shared object file: No such file or directory), missing debuginfos notifications will not be displayed
Missing separate debuginfo for /usr/bin/python3.7
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/66/16[…].debug
Missing separate debuginfo for /lib64/ld-linux-x86-64.so.2
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/53/b6[…].debug
[…]



I could not find this mentioned in any changelog, so I'd like to ask:

- Is this change intended/reasonable? (If so, I'll need to update Python's tests, which verify Python-GDB integration by examining output)
- Is there a way to point stdlog back at stdout?
Comment 1 Sergio Durigan Junior 2019-06-21 19:26:43 UTC 
GDB needed to be rebuilt to use the new librpm.so.9.  gdb-8.3.50.20190610-17.fc31 should fix this problem.  Please reopen the bug if you still see the issue.  Thanks.
Note You need to log in before you can comment on or make changes to this bug.