-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 24 Jun 2004, Trog wrote:
> On Mon, 2004-06-21 at 18:35, Christopher X. Candreva wrote:
> > Segmentation Fault
> Please test with current CVS (as of now).
> Thanks
> -trog
Before proceeding I have to appoligise in advance for this email.
yest
On Mon, 2004-06-21 at 18:35, Christopher X. Candreva wrote:
> Segmentation Fault
Please test with current CVS (as of now).
Thanks
-trog
signature.asc
Description: This is a digitally signed message part
On Mon, 2004-06-21 at 18:35, Christopher X. Candreva wrote:
> Here's the latest crash output:
>
> LibClamAV debug: Recognized Raw mail file
> LibClamAV debug: Starting cli_scanmail(), reclev 3
> LibClamAV debug: in mbox()
> LibClamAV debug: Recognized Raw mail file
> LibClamAV debug: Saving attac
On Mon, 2004-06-21 at 17:57, Christopher X. Candreva wrote:
> Going through the debug output since the last crash, I see about 20 errors
> where a VBA scan dir failed on a "can't open". It seems to be in the same
> context as when the last crash occurred. Here is an example:
>
> LibClamAV debug
Here's the latest crash output:
LibClamAV debug: Recognized Raw mail file
LibClamAV debug: Starting cli_scanmail(), reclev 3
LibClamAV debug: in mbox()
LibClamAV debug: Recognized Raw mail file
LibClamAV debug: Deal with header Received: by clamd
LibClamAV debug: parseEmailHeader 'Received: by cl
Going through the debug output since the last crash, I see about 20 errors
where a VBA scan dir failed on a "can't open". It seems to be in the same
context as when the last crash occurred. Here is an example:
LibClamAV debug: Recognized OLE2 container file
LibClamAV debug: in cli_scanole2()
On Mon, 21 Jun 2004, Trog wrote:
> Are there any files left in this directory:
>
> LibClamAV debug: Saving attachment in
> /tmp/clamav/clamav-5bce8e8e51ede379/textportion
clamav-5bce8e8e51ede379 is no longer there, although there are a number of
leftover directories. I'll see what happens next
On Mon, 2004-06-21 at 17:02, Christopher X. Candreva wrote:
> My server's clamd (0.73) has starting dyeing off regularly again (every
> 10-30 minutes). I've managed to capture some debug information, but somehow
> haven't gotten it to make a core file yet.
>
> Again, compiled under gcc 3.4.0, So
My server's clamd (0.73) has starting dyeing off regularly again (every
10-30 minutes). I've managed to capture some debug information, but somehow
haven't gotten it to make a core file yet.
Again, compiled under gcc 3.4.0, Solaris 8 on UltraSparc hardware (Sun Ultra
2)
Output from running un
