run qemu-system-x86_64 (for this reproducer, no need for any arg) run gdb --pid $(pidof qemu-system-x86_64) This results in Attaching to process 27948 [New LWP 27952] [New LWP 27953] Warning: Cannot insert breakpoint -1. Cannot access memory at address 0x20bf00 (gdb) 0x00007fdf94bcd4b1 in ?? () and the gdb session is non-functional. This started happening with gdb-7.11.1-75.fc24 which is the first gdb 7.11.1 build, downgrading to gdb-7.11-74.fc24 avoids this issue.
136613ef0c6850427317e57be1b644080ff6decb is the first bad commit Author: Pedro Alves <palves> Fix PR gdb/19828: gdb -p <process from a container>: internal error
[patch+7.12] PR gdb/20609 - attach of JIT-debug-enabled inf 7.11.1 regression https://sourceware.org/ml/gdb-patches/2016-09/msg00387.html QA: New testfile: gdb.base/jit-attach-pie.exp
gdb-7.12-0.19.20160929.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-cc57295873
gdb-7.11.1-86.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-eb3ca41e5d
gdb-7.11.1-86.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
gdb-7.12-0.19.20160929.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
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-2016-2737.html