Created attachment 1136764 [details] threadit.c Description of problem: Attaching to a multithreaded process PID which is running inside a container will crash GDB. It is not correct to attach to a containerized PID this way - one should use gdbserver instead due to a missing GDB feature. Still it can happen by an accident and GDB should not crash. Version-Release number of selected component (if applicable): devtoolset-4-gdb-7.11-57.el7.x86_64 How reproducible: Always. Steps to Reproduce: # docker run -ti -v /root:/root docker.io/centos bash Inside docker: # /root/threadit Outside docker: # gdb -p `pidof threadit` (gdb) q Actual results: A debugging session is active. Inferior 1 [process 7483] will be detached. Quit anyway? (y or n) y thread.c:980: internal-error: is_executing: Assertion `tp' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) _ Expected results: A debugging session is active. Inferior 1 [process 7483] will be detached. Quit anyway? (y or n) y Detaching from program: target:/root/redhat/threadit, process 7483 Additional info: Bug #1: The internal error should not happen. Bug #2: One cannot entry anything ('y' or 'n'), GDB does not respond. It is not reproducible with non-threaded process. Attaching a sample multi-threaded process I used for reproducibility. I guess any multithreaded process would suffice.
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://access.redhat.com/errata/RHBA-2016:1144