aboutsummaryrefslogtreecommitdiff
path: root/gdb/hppaobsd-nat.c
diff options
context:
space:
mode:
authorJan Kratochvil <jan.kratochvil@redhat.com>2016-03-17 18:17:30 +0100
committerJan Kratochvil <jan.kratochvil@redhat.com>2016-03-17 18:17:30 +0100
commit708bf0a14b10d801a600759f3ef6d272978ae854 (patch)
tree18788ffb35fa90305eaee3434223c6a02ee78de6 /gdb/hppaobsd-nat.c
parent0d5b594f86aa7c8f38487802f75841460ab705bf (diff)
downloadbinutils-708bf0a14b10d801a600759f3ef6d272978ae854.zip
binutils-708bf0a14b10d801a600759f3ef6d272978ae854.tar.gz
binutils-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/hppaobsd-nat.c')
0 files changed, 0 insertions, 0 deletions