That's exactly what I do. I mean there that when I have nautilus hanging and when I attach gdb to it - I do in terminal: gdb, then: attach ####(nautilus process no.) - it stops at the line like this
[New Thread 0xb6ad1930 (LWP 8125)] and nothing happens then, it doesn't end by the line with (gdb) something like ....... Loaded symbols for /usr/lib/gtk-2.0/2.10.0/engines/libmurrine.so 0xb8075430 in __kernel_vsyscall () (gdb) where I can type "thread apply bt" (in comparison with the succeeded log-file attached above) And everything I type in this terminal window where the gdb attach process didn't finalize correctly - nothing works, I can't even get back my ordinary startup line "(user)@(computername):~$". So, as I described above: - I try to open any nautilus window to start another nautilus process with another process no. - I open another tab in terminal where I attach gdb to this second nautilus process - and this time it succeeds to perform the gdb attach correctly. I don't know why, but when trying to attach gdb to the first hanging nautilus process - it doesn't work. -- Nautilus freezes completely when accessing large exterior hard drive (500Gb) https://bugs.launchpad.net/bugs/316877 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
