On 26/10/14 14:59, Brian Drummond wrote:
> "gdb nautilus" allows me to reproduce the segfault, but doesn't return
> control to the debugger. So the "pool" (is it a process? I can't see it
> in ps ax) containing the error must be elsewhere in the system.
You might need to make sure all nautilus processes have been killed
before starting one under gdb - nautilus probably has some "single
instance" logic going on.
The "pool" thread is not visible in ps, but it's visible in pstree: it's
probably the thread where miscellaneous background jobs that don't have
their own thread are scheduled. For instance:
% pstree -p
...
├─nautilus(9073)─┬─{dconf worker}(9079)
│ ├─{gdbus}(9076)
│ ├─{gmain}(9078)
│ └─{pool}(9077)
...
Process 9073 represents the nautilus process as a whole, and 9073 is
also the thread ID of its main thread; the children in {} are other
threads inside process 9073.
S
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
