Back to bug 1316539
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Jan Kratochvil | 2016-03-10 12:41:31 UTC | Depends On | 1221351 | |
| Libor Miksik | 2016-03-14 12:12:05 UTC | Blocks | 1313485 | |
| Matt Newsome | 2016-06-07 18:44:03 UTC | Blocks | 1297579 | |
| Jan Kratochvil | 2016-08-04 21:39:06 UTC | Status | NEW | ASSIGNED |
| Martin Cermak | 2016-08-05 05:47:39 UTC | QA Contact | qe-baseos-tools | mcermak |
| Jan Kratochvil | 2016-08-05 18:04:09 UTC | Doc Text | It is a copy from RHEL-7.3 Bug 1186918 (except for s/7.3/6.9/): Cause: If the GNU debugger (GDB) is executing inside a Super-Privileged Container (SPC) and attaches to a process that is running in another container on Red Hat Enterprise Linux Atomic Host, GDB does not locate the binary images of the main executable or any shared libraries loaded by the process to be debugged. Consequence: As a consequence, GDB may display error messages relating to files not being present, or being present but mismatched, or GDB may seem to attach correctly but then subsequent commands may fail or display corrupted information. Fix: RHEL-6.9 gdbserver has been extended for seamless support of debugging processes from containers; RHEL-6.9 gdbserver now newly supports packets "qXfer:exec-file:read" and "vFile:setfs". RHEL-6.9 gdb cannot use these packets, for processes from containers it is recommended to use Developer Toolset 4.0 (or higher) GDB with RHEL-6.9 gdbserver (gdbserver can also equivalently come from Developer Toolset). RHEL-6.9 gdb functionality remains the same but it can now suggest using gdbserver if one runs gdb with parameter "-p" (or command "attach") and at the same time GDB detects the process being attached is from a containers. RHEL-7.3 gdb now also suggest using explicit "file" command to specify location of executable of the process from container being debugged. The "file" command does not need to be entered if one uses Developer Toolset 4.0 (or higher) GDB instead. Result: RHEL-6.9 gdbserver provides seamless debugging of processes from containers together with Developer Toolset 4.0 (or higher) GDB. Additionally RHEL-7.3 gdb guides user for debugging of processes from containers if Developer Toolset GDB is not available. |
|
| Jan Kratochvil | 2016-08-17 21:52:46 UTC | Status | ASSIGNED | MODIFIED |
| Fixed In Version | gdb-7.2-92.el6 | |||
| errata-xmlrpc | 2016-08-17 21:55:47 UTC | Status | MODIFIED | ON_QA |
| Jan Kratochvil | 2016-08-30 20:10:31 UTC | Blocks | 1361283 | |
| Arjun Shankar | 2016-11-22 09:36:48 UTC | Status | ON_QA | VERIFIED |
| CC | ashankar | |||
| QA Contact | mcermak | ashankar | ||
| Lenka Špačková | 2017-02-17 15:32:54 UTC | Docs Contact | lkuprova | |
| Doc Text | It is a copy from RHEL-7.3 Bug 1186918 (except for s/7.3/6.9/): Cause: If the GNU debugger (GDB) is executing inside a Super-Privileged Container (SPC) and attaches to a process that is running in another container on Red Hat Enterprise Linux Atomic Host, GDB does not locate the binary images of the main executable or any shared libraries loaded by the process to be debugged. Consequence: As a consequence, GDB may display error messages relating to files not being present, or being present but mismatched, or GDB may seem to attach correctly but then subsequent commands may fail or display corrupted information. Fix: RHEL-6.9 gdbserver has been extended for seamless support of debugging processes from containers; RHEL-6.9 gdbserver now newly supports packets "qXfer:exec-file:read" and "vFile:setfs". RHEL-6.9 gdb cannot use these packets, for processes from containers it is recommended to use Developer Toolset 4.0 (or higher) GDB with RHEL-6.9 gdbserver (gdbserver can also equivalently come from Developer Toolset). RHEL-6.9 gdb functionality remains the same but it can now suggest using gdbserver if one runs gdb with parameter "-p" (or command "attach") and at the same time GDB detects the process being attached is from a containers. RHEL-7.3 gdb now also suggest using explicit "file" command to specify location of executable of the process from container being debugged. The "file" command does not need to be entered if one uses Developer Toolset 4.0 (or higher) GDB instead. Result: RHEL-6.9 gdbserver provides seamless debugging of processes from containers together with Developer Toolset 4.0 (or higher) GDB. Additionally RHEL-7.3 gdb guides user for debugging of processes from containers if Developer Toolset GDB is not available. | "gdbserver" now supports seamless debugging of processes from containers Prior to this update, when *GDB* was executing inside a Super-Privileged Container (SPC) and attached to a process that was running in another container on Red Hat Enterprise Linux Atomic Host, *GDB* did not locate the binary images of the main executable or any shared libraries loaded by the process to be debugged. As a consequence, *GDB* could have displayed error messages relating to files not being present, or being present but mismatched. Also, *GDB* may have seemed to attach correctly, but subsequent commands may have failed or displayed corrupted information. In Red Hat Enterprise Linux 6.9, "gdbserver" has been extended for seamless support of debugging processes from containers. The Red Hat Enterprise Linux 6.9 version of "gdbserver" newly supports the *qXfer:exec-file:read* and *vFile:setfs* packets. However, the Red Hat Enterprise Linux 6.9 version of "gdb" cannot use these packets. The Red Hat Developer Toolset 4.1 (or later) version of "gdb" is recommended for use with containers and with Red Hat Enterprise Linux 6.9 "gdbserver". The Red Hat Developer Toolset version of "gdbserver" can be used as well. Red Hat Enterprise Linux 6.9 "gdb" can now suggest using "gdbserver" when run with the "-p" parameter (or the "attach" command) and when, at the same time, it detects that the process being attached is from a container. Red Hat Enterprise Linux 6.9 "gdb" now also suggests the explicit use of the "file" command to specify the location of the process executable in the container being debugged. The "file" command does not need to be entered when the Red Hat Developer Toolset version of "gdb" is being used instead. With this update, Red Hat Enterprise Linux 6.9 "gdbserver" provides seamless debugging of processes from containers together with Red Hat Developer Toolset 4.1 (or later) "gdb". Additionally, Red Hat Enterprise Linux 6.9 "gdb" guides the user through the debugging of processes from containers when Red Hat Developer Toolset "gdb" is not available. | ||
| Doc Type | Bug Fix | Release Note | ||
| errata-xmlrpc | 2017-03-21 00:21:01 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2017-03-21 09:00:31 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2017-03-21 05:00:31 UTC |
Back to bug 1316539