Quoting Philipp Grosswiler <[EMAIL PROTECTED]>: > trog, > > I could finally manage to get the backtrace you requested... clamd now > fails > almost every 6 hours. here is what I got: >
<snip> Thanks. > > I hope it is useful to you. I still don't know why there are actually 3 > PIDs > for clamd. Could you explain this? I just took the first PID, when I > quit > gdb it was asking me to detach from the process and from that point on > the > other PIDs were not accessible by gdb anymore... > I don't use SuSE, but I expect it's version of ps displays all the threads of a prcoess as processes. So you have 3 threads in clamd, and they are displayed as three processes by ps. I'll have a look at the backtraces and see if anything jumps out. Cheers, -trog ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
