Hide Forgot
Is there business interest in supporting debugging of processes inside RHEL-6 docker guests? Bug 1221351 suggests so but for a comfortable debugging one needs to also access files inside the docker guests - which is what is Bug is about. It is not about docker RHEL-6 hosts as those are not supported: https://access.redhat.com/solutions/1378023.
So, I tried this with a RHEL build of gdb-gdbserver-7.2-92.el6.x86_64 running on a CentOS6 docker image - and a RHEL-7 host with DTS-4.1 gdb (devtoolset-4-gdb-7.11-67.el7.x86_64) installed. With the older gdb-gdbserver-7.2-90.el6 running in the docker container, I got the expected error when trying to debug remotely from the host: "warning: Could not load vsyscall page because no executable was specified" - among several related warnings, like: "warning: Remote gdbserver does not support determining executable automatically." With the fixed gdb-gdbserver-7.2-92.el6, running in the docker container I got: "Reading /root/a.out from remote target..." ... and additional details in the stack trace. So, this is indeed fixed => moving this bug to VERIFIED. Finally: bcause this involves installing a RHEL-6 docker image in RHEL-7, it isn't really worth checking in an automated test for it.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2017-0572.html