Description of problem: Was trying to run gdb against docker and I notice I can't install debuginfo packages for docker like I can for etcd (BZ#1184257). Also when I try to run gdb against docker I get a messed up path to files (like BZ#1184221 illustrates for etcd). [root@localhost]# gdb /usr/bin/docker GNU gdb (GDB) Fedora 7.9.1-16.fc22 Copyright (C) 2015 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-redhat-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/bin/docker...done. (gdb) l 1 /usr/src/debug/github.com/docker/docker/pkg/term/_obj/_cgo_export.c: No such file or directory. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: [root@localhost]# debuginfo-install docker ... Could not find debuginfo for main pkg: docker-1.6.0-3.git9d26a07.fc22.x86_64 ... Additional info: [root@localhost]# rpm -q docker gdb golang-src docker-1.6.0-3.git9d26a07.fc22.x86_64 gdb-7.9.1-16.fc22.x86_64 golang-src-1.4.2-2.fc22.noarch
Hi Dusty, at the moment it is not possible to strip debug info from docker binary as during building the binary is embedded with a SHA string. When the binary is stripped computed SHA is changed and thus does not equal the embedded one. We are working on it. I will keep this issue open and sent new information when available. Kind Regards Jan
Any update?
Still no change.
I think this has gotten better in docker-1.9.
Looks like there aren't separate golang debugging packages in rawhide at least for Docker, moving there.
docker seems to be working when built with debuginfo subpackage. Can someone verify and run some tests on the docker binaries? Plus take a look at debug data if they are at least good enough? http://koji.fedoraproject.org/koji/taskinfo?taskID=12449885
Fixed in docker-1.10
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.