On 5/11/16 9:14 AM, Warren Young wrote:
On May 11, 2016, at 10:10 AM, Mike Bonnet wrote:
On 5/11/16 8:18 AM, Yaakov Selkowitz wrote:
On 2016-05-11 09:35, Mike Bonnet wrote:
Any chance we could get a new 64-bit build?
We'd need to find the real cause of this before it would be of any help.
I'd start with updating to 0.99.2, however we borrow Fedora's -norar
sources but they haven't bumped yet (#1333949).
I'll retry with 0.99.2 when it's available.
Or you could rebuild 0.99.1 from the sources and see if that fixes the symptom.
If it does, you have a reason to reject Yaakov’s answer. If not, Yaakov was
right to disbelieve your hypothesis.
The build issue was a red herring, sorry about that. It turns out a
specific file, xdate.exe, is causing clamscan to segfault. This is an
old file, from 2012, used for date formatting, but it has just started
causing problems. I've reproduced the segfault in 0.99.1-1 and 0.98.7-2
running on Cygwin64 on Windows Server 2012, but didn't go any further
back than that. I've verified that there are no viruses in the file
(according to virustotal.com):
https://virustotal.com/en/file/937800ed6b0408b9dba4e4dc507cd0b1962d3adb6285947db520009d19cbe24e/analysis/1463097443/
The file is here (it's listed as "free for any use"):
http://people.redhat.com/mikeb/clamscan-segfault/xdate.exe
The output from running "clamscan --debug xdate.exe" is here:
http://people.redhat.com/mikeb/clamscan-segfault/clamscan-debug-xdate.log
and the stackdump is here:
http://people.redhat.com/mikeb/clamscan-segfault/clamscan.exe.stackdump
Sounds like this should be reported to Clamav upstream. Is anyone
involved with Clamav already, that could report this to the right
people, or do I need to start signing up for mailing lists? :)
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
