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: Root EntryLibClamAV debug: [root]LibClamAV > debug: bLibClamAV debug: 0 0 > LibClamAV debug: _5_SummaryInformationLibClamAV debug: [file]LibClamAV > debug: bLibClamAV debug: 4096 0 > LibClamAV debug: WorkbookLibClamAV debug: [file]LibClamAV > debug: bLibClamAV debug: 99316 0 > LibClamAV debug: _5_DocumentSummaryInformationLibClamAV debug: [file]LibClamAV > debug: bLibClamAV debug: 4096 0 > LibClamAV debug: VBA scan dir: /tmp/clamav/clamav-d3a98e07086bc832 > LibClamAV debug: in vba56_dir_read() > LibClamAV debug: Can't open /tmp/clamav/clamav-d3a98e07086bc832/_VBA_PROJECT > LibClamAV debug: Open WordDocument failed
These are harmless. It just means there wasn't any macro code in the document. -trog
signature.asc
Description: This is a digitally signed message part
