Re: Thunderbird and Nautilus having problems
Josh Hansen <doctorj@softhome.net> writes:
> Hi all,
> I made a debug-enabled build of nautilus (I think I got debug enabled,
> anyway) and now I have a slightly more meaningful backtrace. This is
> what bug buddy gives me right when nautilus starts up:
>
> ------
> Backtrace was generated from '/usr/bin/nautilus'
>
> Using host libthread_db library "/lib/libthread_db.so.1".
> [Thread debugging using libthread_db enabled]
> [New Thread 16384 (LWP 22815)]
> [New Thread 32769 (LWP 22816)]
> [Thread debugging using libthread_db enabled]
> [New Thread 16384 (LWP 22815)]
> [New Thread 32769 (LWP 22816)]
> [Thread debugging using libthread_db enabled]
> [New Thread 16384 (LWP 22815)]
> [New Thread 32769 (LWP 22816)]
> [New Thread 16386 (LWP 22817)]
> 0x0000002a96c2fa43 in waitpid () from /lib/libpthread.so.0
> #0 0x0000002a96c2fa43 in waitpid () from /lib/libpthread.so.0
> #1 0x0000002a96529a4c in libgnomeui_module_info_get ()
> from /usr/lib/libgnomeui-2.so.0
> #2 0x0000002a96c2e84e in __pthread_sighandler () from /lib/libpthread.so.0
> #3 <signal handler called>
> -----
>
> I'm no expert at reading this information, but is it telling me that
> in libgnomeui-2 there is a function called module_info_get() where the
> problem is originating? Or is it in libpthread? Thanks for any tips to
> a novice like myself :-)
>
> -- Josh
No, you just got a signal. Seeing the code is in waitpid you probably
got a SIGCHILD. Continue until you hit the actual segfault.
MfG
Goswin
Reply to: