|Summary:||invalid gdb header|
|Product:||[Fedora] Fedora||Reporter:||xdegaye <xdegaye>|
|Component:||gdb||Assignee:||Jan Kratochvil <jan.kratochvil>|
|Status:||CLOSED ERRATA||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||18||CC:||gbenson, jan.kratochvil, palves, pmuldoon, sergiodj, tromey|
|Fixed In Version:||gdb-7.6.1-41.fc19||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2013-09-23 00:30:10 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description xdegaye 2013-09-05 20:09:04 UTC
Description of problem: The Fedora gdb header is: GNU gdb (GDB) Fedora (7.6-32.fc19) This is non conformant to GNU coding standards as specified in section 4.7.1 of http://www.gnu.org/prep/standards/standards.html: "The first line is meant to be easy for a program to parse; the version number proper starts after the last space." ^^^^^^^^^^^^^^^^^^^^ See http://stackoverflow.com/questions/18157954/fedora-19-pyclewn-cant-find-gdb-version for why this is an annoying bug. Version-Release number of selected component (if applicable): Version 7.6-32.fc19 How reproducible: Steps to Reproduce: 1. Run: gdb --version Actual results: GNU gdb (GDB) Fedora (7.6-32.fc19) Expected results: GNU gdb (GDB) Fedora 7.6-32.fc19
Comment 1 xdegaye 2013-09-05 20:19:01 UTC
Note that this is the only mean provided by gdb, for front-ends to learn the gdb version they are running, wether they are interfacing with the cli or with gdb/mi. This is the reason why this line MUST strictly conform to the GNU coding standards.
Comment 2 Jan Kratochvil 2013-09-09 16:07:41 UTC
It no longer prints the exception "cannot find the gdb version" although pyclewn fails here on some other error.
Comment 3 Fedora Update System 2013-09-09 16:33:21 UTC
gdb-7.6.1-41.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/gdb-7.6.1-41.fc19
Comment 4 Fedora Update System 2013-09-09 16:33:26 UTC
gdb-7.5.1-42.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/gdb-7.5.1-42.fc18
Comment 5 Fedora Update System 2013-09-09 16:33:29 UTC
gdb-184.108.40.20630731-10.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/gdb-220.127.116.1130731-10.fc20
Comment 6 Fedora Update System 2013-09-09 23:54:01 UTC
Package gdb-7.5.1-42.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gdb-7.5.1-42.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-16214/gdb-7.5.1-42.fc18 then log in and leave karma (feedback).
Comment 7 xdegaye 2013-09-10 10:05:24 UTC
Running debian, so I cannot yum or even use the downloaded and extracted binary from http://koji.fedoraproject.org/koji/buildinfo?buildID=463174 (missing shared library). Since this is the only change at http://pkgs.fedoraproject.org/cgit/gdb.git/commit/?h=f18 I did check that pyclewn 1.10 (the latest stable release) now runs fine after changing the version.in file of upstream gdb 7.5.1 to: Red Hat Enterprise Linux 7.5.1-42.fc18 or Fedora 7.5.1-42.fc18 Don't know if this is good enough for a karma.
Comment 8 Jan Kratochvil 2013-09-10 10:11:29 UTC
(In reply to xdegaye from comment #7) > Don't know if this is good enough for a karma. It is not but anyway thanks for the bugreport.
Comment 9 Fedora Update System 2013-09-23 00:30:10 UTC
gdb-18.104.22.16830731-10.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
Comment 10 Fedora Update System 2013-09-24 23:00:40 UTC
gdb-7.5.1-42.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
Comment 11 Fedora Update System 2013-09-24 23:02:29 UTC
gdb-7.6.1-41.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.