diff options
| author | Jan Kratochvil <jan.kratochvil@redhat.com> | 2016-03-17 18:17:30 +0100 |
|---|---|---|
| committer | Jan Kratochvil <jan.kratochvil@redhat.com> | 2016-03-17 18:17:30 +0100 |
| commit | 708bf0a14b10d801a600759f3ef6d272978ae854 (patch) | |
| tree | 18788ffb35fa90305eaee3434223c6a02ee78de6 /gdb/linux-thread-db.c | |
| parent | 0d5b594f86aa7c8f38487802f75841460ab705bf (diff) | |
| download | gdb-708bf0a14b10d801a600759f3ef6d272978ae854.zip gdb-708bf0a14b10d801a600759f3ef6d272978ae854.tar.gz gdb-708bf0a14b10d801a600759f3ef6d272978ae854.tar.bz2 | |
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.
Diffstat (limited to 'gdb/linux-thread-db.c')
| -rw-r--r-- | gdb/linux-thread-db.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/gdb/linux-thread-db.c b/gdb/linux-thread-db.c index ce60beb..992965f 100644 --- 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.")); } } } |