diff options
author | Daniel Colascione <dancol@dancol.org> | 2014-11-11 14:18:23 +0000 |
---|---|---|
committer | Pedro Alves <palves@redhat.com> | 2014-11-11 14:18:23 +0000 |
commit | 015de6884f6fdebaffd4b7d4c7f14fb4d5fc0bb1 (patch) | |
tree | 2da776a486bf382e28d662023ed756b60a562f46 /gdb/linux-thread-db.c | |
parent | 0ac2337434968896a6393fdd8c0624bd2945bbea (diff) | |
download | gdb-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 'gdb/linux-thread-db.c')
-rw-r--r-- | gdb/linux-thread-db.c | 29 |
1 files changed, 29 insertions, 0 deletions
diff --git a/gdb/linux-thread-db.c b/gdb/linux-thread-db.c index 352fac1..c49b567 100644 --- a/gdb/linux-thread-db.c +++ b/gdb/linux-thread-db.c @@ -1217,12 +1217,41 @@ thread_db_new_objfile (struct objfile *objfile) check_for_thread_db (); } +static void +check_pid_namespace_match (void) +{ + /* Check is only relevant for local targets targets. */ + if (target_can_run (¤t_target)) + { + /* If the child is in a different PID namespace, its idea of its + PID will differ from our idea of its PID. When we scan the + child's thread list, we'll mistakenly think it has no threads + since the thread PID fields won't match the PID we give to + libthread_db. */ + char *our_pid_ns = linux_proc_pid_get_ns (getpid (), "pid"); + char *inferior_pid_ns = linux_proc_pid_get_ns ( + ptid_get_pid (inferior_ptid), "pid"); + + if (our_pid_ns != NULL && inferior_pid_ns != NULL + && strcmp (our_pid_ns, inferior_pid_ns) != 0) + { + warning (_ ("Target and debugger are in different PID " + "namespaces; thread lists and other data are " + "likely unreliable")); + } + + xfree (our_pid_ns); + xfree (inferior_pid_ns); + } +} + /* This function is called via the inferior_created observer. This handles the case of debugging statically linked executables. */ static void thread_db_inferior_created (struct target_ops *target, int from_tty) { + check_pid_namespace_match (); check_for_thread_db (); } |