[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: kbuildsycoca crashes
From:       Wilco Greven <j.w.greven () student ! utwente ! nl>
Date:       2002-02-25 15:43:04
[Download RAW message or body]

On Mon, Feb 25, 2002 at 04:24:02PM +0100, jonathan_brugge wrote:
> I noticed the problem with FAM too, it crashes when calling libfam.so, 
> according to my backtrace:
> 
> [New Thread 1024 (LWP 1607)]
> 0x41015b79 in wait4 () from /lib/libc.so.6
> #0  0x41015b79 in wait4 () from /lib/libc.so.6
> #1  0x4108e068 in __check_rhosts_file () from /lib/libc.so.6
> #2  0x40e72263 in waitpid () from /lib/libpthread.so.0
> #3  0x406101fa in KCrash::defaultCrashHandler(int) (sig=2) at kcrash.cpp:224
> #4  0x40f9e928 in sigaction () from /lib/libc.so.6
> #5  0x40eac694 in __dynamic_cast () from /usr/lib/libfam.so.0
> #6  0x4029ca17 in KBuildServiceGroupFactory::addNewEntry(QString const&, 
char 
> const*, KSycocaEntry*) (this=0xbfffff45, file=@0xbfffffb8, resource=0x0, 
>     newEntry=0x10) at kbuildservicegroupfactory.cpp:72
> #7  0x40f8e6cf in __libc_start_main () from /lib/libc.so.6
> 
> I'm using the libfam that comes with Debian unstable, which I'm quite sure 
is 
> not compiled with the same compiler I used to compile KDE with (3.0.4). 
AFAIK 
> all Debian-packages use 2.95. 

Yes, this is exactly the same setup as mine.

> Is it possible to let only kbuildsycoca use polling and the rest of KDE FAM? 
> I suppose not, but as libfam is said to give a lower load I'd prefer to use 
> it...

No, this affects all programs which link to fam. But if you disable fam,
KDirWatch will use DNOTIFY instead (AFAIK you need a 2.4.* kernel for this). 

Greetings,
Wilco


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]