nonsensical output in report.txt

Avast Business Avast Business for Linux
1

I see huge nonsensical filecounts in report.txt

With avastgui (Linux home edition 1.3.0) I scanned a folder in my home directory.
It contains two subfolders and two files
One subfolder contains three files
the other subfolder contains two files
Thus:
total folders: 3
total files: 10

The avastgui window reports:

number of scanned files/folders: 15/0
number of infected files: 0
total size of scanned files: 3.8 MiB

the log file report.txt reports:

  • avast! Report
  • This file is generated automatically
  • Started on ma 09 aug 2010 10:28:40 CEST
  • VPS: 100807-1, 07-08-10

Infected files: 450971566080
Total files: 450971566081
Total folders: 450971566081
Total size: 0,0 MiB

REMARKS

  1. The values in the log file are completely wrong.
  2. the value of “number of scanned files/folders” in avastgui seems to be wrong.

QUESTIONS

  1. Are there more users who have this sort of output?
  2. Can this problem be solved?
2

This is ocassionally found in the Wx-Widgetised version. Hard to reproduce, valgirnd doesn’t identify uninitialised data, and the effect is non-deterministic. Please, could you specify which system do you have, what kernel, and cpu/mem configuration? Just to get a clue.

regards,
pc

3

operating system:
Ubuntu 10.04 LTS
( updated Edubuntu 7 through 8.04 )

kernel:
$ uname -r
2.6.32-23-generic
$ uname -a
2.6.32-23-generic #37-Ubuntu SMP Fri Jun 11 07:54:58 UTC 2010 i686 GNU/Linux

cpu:
$ less /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 107
model name : AMD Athlon™ 64 X2 Dual Core Processor 3600+
stepping : 1
cpu MHz : 1908.776
cache size : 512 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch
bogomips : 3817.55
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc 100mhzsteps

mem:
Two banks of Corsair 1024MB, DDR2
$ lshw -c Memory
*-memory:0
description: System memory
physical id: 3
size: 2012MiB
*-cache:0
description: L1 cache
physical id: 0
size: 128KiB
*-cache:1
description: L2 cache
physical id: 1
size: 512KiB
*-memory:1 UNCLAIMED
description: RAM memory
product: MCP55 Memory Controller
vendor: nVidia Corporation
physical id: 0
bus info: pci@0000:00:00.0
version: a1
width: 32 bits
clock: 66MHz (15.2ns)
capabilities: bus_master cap_list
configuration: latency=0
*-memory:2 UNCLAIMED
description: RAM memory
product: MCP55 Memory Controller
vendor: nVidia Corporation
physical id: 1.2
bus info: pci@0000:00:01.2
version: a2
width: 32 bits
clock: 66MHz (15.2ns)
configuration: latency=0

4

And, is the result the same, when you run it under different user, or when runnuing it under strace/gdb? I spotted this flaw once or twice, but I was unable to reproduce it in a deterministic manner, to be able to found the cause.

regards,
pc

5

different user: same erroneous output
different ubuntu install (8.04): same erroneous output

I don’t have experience with these tools.
Any suggestion how to use them?

Cheers, A

6

just issue command as before, but prepend strace -f, and append >output 2>&1

pc

7

hello zilog,

Excuses for my long silence.
I noticed that the commandline version “avast” DOES give correct output in its logfile. Hence I use that version.

Hard to reproduce, valgirnd doesn't identify uninitialised data
I agree with you that this is probably an initialisation problem.

Unfortunately, I donot have the time at present to pursue this matter further in detail.
Regards, A