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

List:       kde-devel
Subject:    Kicker / famd bug
From:       Gregor Jasny <gjasny () wh8 ! tu-dresden ! de>
Date:       2002-05-14 21:16:09
[Download RAW message or body]

Hi,

Today my kicker (KDE 3.0.1 CVS>27.03.2002) deadlocked with famd.

An attached strace to the kicker kdeinit process showed the following:

It loopes through:

[snip]
lstat64("/dev/radio63", {st_mode=S_IFCHR|0660, st_rdev=makedev(81, 127), ...}) 
= 0
lstat64("/dev/vtx22-", {st_mode=S_IFCHR|0660, st_rdev=makedev(81, 214), ...}) 
= 0
[a lot of lstat64 and stat64]
access("/dev/dri/.directory", F_OK)     = -1 ENOENT
gettimeofday({1021409555, 257663}, NULL) = 0
access("/dev/fd/.directory", F_OK)      = -1 ENOENT
gettimeofday({1021409555, 266295}, NULL) = 0
access("/dev/ida/.directory", F_OK)     = -1 ENOENT
[more access, gettimeofday ...]
[more lstat ...]

The complete strace snapshot is available from
http://hell.wh8.tu-dresden.de/~gjadm/

Both the kicker and the famd process took 50% CPU time.

Is this a known bug?
Should I file a bug report against this?

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