Startup hang

Vladimir Prus ghost at cs.msu.su
Thu Nov 30 08:42:11 UTC 2006


On Thursday 30 November 2006 11:32, Andras Mantia wrote:
> On Thursday 30 November 2006 09:12, Vladimir Prus wrote:
> > I don't expect anybody to be able to debug given such profuse
> > information, but I'm hoping somebody saw this before. This is rare
> > bug, but as soon as I hit it I can't get kdevelop to start except by
> > rebooting.
> 
> Is the backtrace the same if you don't attach to kdevelop, but start 
> kdevelop directly from gdb?

Yes:

(gdb) where
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb61d57d1 in connect () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb61de5f6 in ?? () from /usr/lib/libfam.so.0
#3  0x00000011 in ?? ()
#4  0xbf945a0a in ?? ()
#5  0x0000006e in ?? ()
#6  0x00000000 in ?? ()

Perhaps this means that fam daemon has died, but kdevelop does not notice that?

- Volodya





More information about the KDevelop-devel mailing list