<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">Hi Török,<br><br>please find my answers in your text below.<br><br><br><span style="color: rgb(0, 128, 255);">Am 12 Jan 2011 um 17:19 hat Török Edwin geschrieben:</span><br style="color: rgb(0, 128, 255);"><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">Datum: Wed, 12 Jan 2011 17:19:21 +0200</span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">Von: Török Edwin <edwin@clamav.net></span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">An: Andreas Jörg <ajoerg123@yahoo.de></span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">Kopie
an: 609759@bugs.debian.org</span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">Betreff: Re: Bug#609759 - further files 1</span><br style="color: rgb(0, 128, 255);"><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> On 2011-01-12 14:39, Andreas Jörg wrote:</span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> > Please find attached the clamav-log files as well as the windows</span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> file on</span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> > which the scan crahes.</span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> > </span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128,
255);">> > I will also provide the output of gdb /usr/bin/clamscan -c</span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> core.9723.</span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> </span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> Thanks for the core file, it is a similar bug as last time.</span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> </span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> Can you please run these commands:</span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> $ cd /tmp</span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> $ sigtool --unpack-current bytecode</span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> $ clambc -- --debug 767944.cbc
2>log</span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);"><br><span style="color: rgb(255, 0, 0);">I tried that, the logfile only contains "Unable to load --".<br><br>The reason is probably, that 767944.cbc ist not a valid filename here.<br><br>Please find a list of the files in /tmp as attachment 1.<br><br></span><br>> </span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> Then send me the file called 'log', make sure it contains CMOV, or</span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> CMOVE, if not try another .cbc files from /tmp.</span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> </span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> Crash is here:</span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> Dump of assembler code from 0xb16e58ac to
0xb16e58b6:</span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> => 0xb16e58ac: 0f 44 f0 cmove %eax,%esi</span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> 0xb16e58af: 84 db test %bl,%bl</span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> 0xb16e58b1: 0f 85 80 ff ff ff jne 0xb16e5837</span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> </span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> I don't understand why though, the pattern for CMOV is guarded by</span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> a</span><br style="color: rgb(0, 128, 255);"><span style="color:
rgb(0, 128, 255);">> CPUID test.</span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> Could you install the 'x86info' package, and run this (as root):</span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> # modprobe cpuid</span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> # x86info -a</span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> </span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> And send me the output from x86info -a.</span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> <br><br><span style="color: rgb(255, 0, 0);">"x86info -a > /root/2011-01-12_x86info.output" gave the following error message on the console: "/dev/cpu/0/msr: No such file or directory"<br><br>Please find x86info.output attached too.<br></span><br><br style="color:
rgb(0, 128, 255);"></span><span style="color: rgb(0, 128, 255);">> Best regards,</span><br style="color: rgb(0, 128, 255);"><span style="color: rgb(0, 128, 255);">> --Edwin<br><br><br><span style="color: rgb(255, 0, 0);">Best regards,<br><br>Andreas Joerg<br></span></span></td></tr></table><br>