On 2011-01-12 14:39, Andreas Jörg wrote: > Please find attached the clamav-log files as well as the windows file on > which the scan crahes. > > I will also provide the output of gdb /usr/bin/clamscan -c core.9723.
Thanks for the core file, it is a similar bug as last time. Can you please run these commands: $ cd /tmp $ sigtool --unpack-current bytecode $ clambc -- --debug 767944.cbc 2>log Then send me the file called 'log', make sure it contains CMOV, or CMOVE, if not try another .cbc files from /tmp. Crash is here: Dump of assembler code from 0xb16e58ac to 0xb16e58b6: => 0xb16e58ac: 0f 44 f0 cmove %eax,%esi 0xb16e58af: 84 db test %bl,%bl 0xb16e58b1: 0f 85 80 ff ff ff jne 0xb16e5837 I don't understand why though, the pattern for CMOV is guarded by a CPUID test. Could you install the 'x86info' package, and run this (as root): # modprobe cpuid # x86info -a And send me the output from x86info -a. Best regards, --Edwin _______________________________________________ Pkg-clamav-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-clamav-devel
