Quoting Philipp Grosswiler <[EMAIL PROTECTED]>:
> > LinuxThreads are based on processes - the three processes
> > are: the main thread of clamd, threadwatcher (from clamd) and
> > thread-manager (always spawned by LinuxThreads).
>
> So it is correct to only use gdb with the first process (main
> LinuxThreads are based on processes - the three processes
> are: the main thread of clamd, threadwatcher (from clamd) and
> thread-manager (always spawned by LinuxThreads).
So it is correct to only use gdb with the first process (main thread of
clamd)? Or is it necessary to also include backtr
On Thu, 15 Jan 2004 13:32:56 +0100
"Philipp Grosswiler" <[EMAIL PROTECTED]> wrote:
> trog,
>
> I could finally manage to get the backtrace you requested... clamd now
> fails almost every 6 hours. here is what I got:
Thank you for the backtrace.
> I hope it is useful to you. I still don't know w
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:
>
Thanks.
>
> I hope it is useful to you. I still don't know why there are actually 3
> PIDs
> for clamd. Co
trog,
I could finally manage to get the backtrace you requested... clamd now fails
almost every 6 hours. here is what I got:
(gdb) bt
#0 0x40093b94 in __pthread_sigsuspend () from /lib/i686/libpthread.so.0
#1 0x400939d8 in __pthread_wait_for_restart_signal () from
/lib/i686/libpthread.so.0
#2
