Suggest running gdbserver for a PID in container

currently
	gdb -p <pid from a container>
will print:
	warning: Target and debugger are in different PID namespaces; thread lists and other data are likely unreliable

It correctly states the problem but it does not say how to solve it.

Originally I wanted to suggest also the Docker "-p 1234:1234" parameter but
I see the containers are more general topic than just Docker (even LxC etc.).

According to Gary future GDBs should be able to work even without gdbserver.
But currently gdbserver is still required.

gdb/ChangeLog
2016-03-17  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* linux-thread-db.c (check_pid_namespace_match): Extend the message.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index f5099d93f91829b919cee7c44d0f60c52979aad4..2df6ccd7fa3ce9cb5d59710842a355faf567b07f 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2016-03-17  Jan Kratochvil  <jan.kratochvil@redhat.com>
+
+       * linux-thread-db.c (check_pid_namespace_match): Extend the message.
+
 2016-03-17  Pedro Alves  <palves@redhat.com>
            Don Breazeal  <donb@codesourcery.com>
 

diff --git a/gdb/linux-thread-db.c b/gdb/linux-thread-db.c
index ce60bebe3c9c092cf3fec068bf0b586e95985db0..992965ff5d2c918a3750b525a4a9ee69ad365f7c 100644 (file)
--- a/gdb/linux-thread-db.c
+++ b/gdb/linux-thread-db.c
@@ -1024,7 +1024,8 @@ check_pid_namespace_match (void)
        {
          warning (_ ("Target and debugger are in different PID "
                      "namespaces; thread lists and other data are "
-                     "likely unreliable"));
+                     "likely unreliable.  "
+                     "Connect to gdbserver inside the container."));
        }
     }
 }