On Sun, 2004-02-29 at 17:55, Philipp Grosswiler wrote:
OK, now I got something for you... but could be that the problem is already
solved in the latest CVS version... just that the latest CVS is not working
for me (see my earlier post about readdb()).
(gdb) continue
Continuing.
[New
On Mon, 2004-03-01 at 10:37, Philipp Grosswiler wrote:
Hello Trog.
The libpthread thread manager seg faulted. I've never seen that happen
before. I guess that would be either a bug in libpthread or some very
bad memory corruption somewhere.
Well, this happened about 2-3 times
Set your thread timeout to zero. Setting this to any other value causes
users with dialup connections to timeout while sending attachments, in
addition my seg faults are gone. This is the best reason to do this,
I've been running for 4 days now without a single crash, previoiusly I
was
On Mon, 2004-03-01 at 14:04, Loren Salsgiver wrote:
Set your thread timeout to zero. Setting this to any other value causes
users with dialup connections to timeout while sending attachments, in
addition my seg faults are gone. This is the best reason to do this,
I've been running for 4
On Mon, 2004-03-01 at 10:37, Philipp Grosswiler wrote:
Well, this happened about 2-3 times (before, I was not able to use gdb). But
I am using the current CVS snapshot (20040229) and it is working great until
now. I didn't have any crashes since then. Could be that it is already
solved in this
OK, now I got something for you... but could be that the problem is already
solved in the latest CVS version... just that the latest CVS is not working
for me (see my earlier post about readdb()).
3. Wait for a seg fault. Then issue the backtrace command.
That happened right now.
4. If may
OK, this is the last time I will post about the occurance of this problem:
Thu Feb 26 23:57:01 2004 - stream: Worm.SomeFool FOUND
Thu Feb 26 23:57:12 2004 - Segmentation fault :-( Bye..
Fri Feb 27 00:23:42 2004 - SelfCheck: Database status OK.
Fri Feb 27 00:37:08 2004 - ERROR: accept() failed
Fri
On Fri, 2004-02-27 at 07:59, Philipp Grosswiler wrote:
OK, this is the last time I will post about the occurance of this problem:
Thu Feb 26 23:57:01 2004 - stream: Worm.SomeFool FOUND
Thu Feb 26 23:57:12 2004 - Segmentation fault :-( Bye..
Fri Feb 27 00:23:42 2004 - SelfCheck: Database
Hello Trog.
In order to track this problem down, we would need you to do the
following:
1. Run clamd in debug mode:
/usr/local/sbin/clamd --debug
2. Attach gdb to the running clamd process
gdb /usr/local/sbin/clamd process id
then in gdb, issue the command
On Fri, 2004-02-27 at 13:32, Philipp Grosswiler wrote:
Hello Trog.
In order to track this problem down, we would need you to do the
following:
1. Run clamd in debug mode:
/usr/local/sbin/clamd --debug
2. Attach gdb to the running clamd process
gdb
10 matches
Mail list logo
