[Bug gdb/18368] gdb with nsenter attaches to wrong process

["raghu.prabhu13 at gmail dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=18368

--- Comment #4 from Raghavendra <raghu.prabhu13 at gmail dot com> ---
So, I did try with namespaces branch and it works great.


sudo gdb -p 31802
GNU gdb (GDB) 7.9.50.20150429-cvs
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
Attaching to process 31802
Reading symbols from target:/usr/bin/sleep...Reading symbols from
target:/usr/bin/sleep...(no debugging symbols found)...done.
(no debugging symbols found)...done.
Reading symbols from target:/lib64/libc.so.6...(no debugging symbols
found)...done.
Reading symbols from target:/lib64/ld-linux-x86-64.so.2...(no debugging symbols
found)...done.

warning: Target and debugger are in different PID namespaces; thread lists and
other data are likely unreliable
0x00007fdaa0a74470 in __nanosleep_nocancel () from target:/lib64/libc.so.6
(gdb) bt
#0  0x00007fdaa0a74470 in __nanosleep_nocancel () from target:/lib64/libc.so.6
#1  0x0000000000403e5f in rpl_nanosleep ()
#2  0x0000000000403cc0 in xnanosleep ()
#3  0x00000000004016cd in main ()
(gdb) quit
A debugging session is active.

        Inferior 1 [process 31802] will be detached.

Quit anyway? (y or n) y
Detaching from program: target:/usr/bin/sleep, process 31802

==================

a) I also verified this from inside container by installing gdb there. (You
need a privileged container for that which is strange).

b) It still shows  the warning - "warning: Target and debugger are in different
PID namespaces; thread lists and other data are likely unreliable", is it still
required?


c) Also, -Werror build fails for that branch:
https://github.com/gbenson/binutils-gdb/issues/1


Thanks.

-- 
You are receiving this mail because:
You are on the CC list for the bug.