aboutsummaryrefslogtreecommitdiff
path: root/bfd
diff options
context:
space:
mode:
authorDaniel Colascione <dancol@dancol.org>2014-11-11 14:18:23 +0000
committerPedro Alves <palves@redhat.com>2014-11-11 14:18:23 +0000
commit015de6884f6fdebaffd4b7d4c7f14fb4d5fc0bb1 (patch)
tree2da776a486bf382e28d662023ed756b60a562f46 /bfd
parent0ac2337434968896a6393fdd8c0624bd2945bbea (diff)
downloadgdb-015de6884f6fdebaffd4b7d4c7f14fb4d5fc0bb1.zip
gdb-015de6884f6fdebaffd4b7d4c7f14fb4d5fc0bb1.tar.gz
gdb-015de6884f6fdebaffd4b7d4c7f14fb4d5fc0bb1.tar.bz2
Warn users about mismatched PID namespaces
Linux supports multiple "PID namespaces". Processes in different PID namespaces have different views of the system process list. Sometimes, a single process can appear in more than one PID namespace, but with a different PID in each. When GDB and its target are in different PID namespaces, various features can break due to the mismatch between what the target believes its PID to be and what GDB believes its PID to be. The most visible broken functionality is thread enumeration silently failing. This patch explicitly warns users against trying to debug across PID namespaces. The patch introduced no new failures in my test suite run on an x86_64 installation of Ubuntu 14.10. It doesn't include a test: writing an automated test that exercises this code would be very involved because CLONE_NEWNS requires CAP_SYS_ADMIN; the easier way to reproduce the problem is to start a new lxc container. gdb/ 2014-11-11 Daniel Colascione <dancol@dancol.org> Warn about cross-PID-namespace debugging. * nat/linux-procfs.h (linux_proc_pid_get_ns): New prototype. * nat/linux-procfs.c (linux_proc_pid_get_ns): New function. * linux-thread-db.c (check_pid_namespace_match): New function. (thread_db_inferior_created): Call it.
Diffstat (limited to 'bfd')
0 files changed, 0 insertions, 0 deletions