Here is a gdb output.

Procedure I followed :

1) installed nautilus-dbgsym like described in  
https://wiki.ubuntu.com/DebuggingProgramCrash
2) relaunched nautilus
3) attached a gdb to nautilus, change gdb options as said in 
https://wiki.ubuntu.com/Backtrace
4) went to  ~/tmp with nautilus, clicked on "display as list", nautilus hung up
5) sent a signal 4 to nautilus process
6) display backtrace and registers

It seems to freeze in __lll_mutex_lock_wait ()  from 
/lib/tls/i686/cmov/libpthread.so.0.
Please confirm this is the right procedure. Especially, why do I have so many 
"No symbol table info available" ? Is sending a signal 4 to the frozen process 
a good thing?

** Attachment added: "output of a gdb attached to the nautilus when freezing 
killed with signal 4"
   http://launchpadlibrarian.net/14490536/gdb-nautilus.txt

-- 
Nautilus freeze when displaying a directory by "list"
https://bugs.launchpad.net/bugs/229554
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to