This is the mail archive of the
mailing list for the Cygwin project.
Re: [ANNOUNCEMENT] clamav 0.99.1-1
- From: Yaakov Selkowitz <yselkowitz at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 13 May 2016 17:14:37 -0500
- Subject: Re: [ANNOUNCEMENT] clamav 0.99.1-1
- Authentication-results: sourceware.org; auth=none
- References: <announce dot 201603301732 dot u2UHW4eN011967 at int-mx11 dot intmail dot prod dot int dot phx2 dot redhat dot com> <6da62132-1e66-41c9-043d-c552f4faf1c3 at redhat dot com> <4f86f77b-e2cb-b654-760b-499623dd61a1 at cygwin dot com> <360d98a0-8e44-e816-ea44-d87a2e2655a4 at redhat dot com> <91F687B2-C7E2-444D-91C3-2FAD580955A2 at etr-usa dot com> <d165fc48-cf32-6e55-9bfa-d727899dcc76 at redhat dot com>
On 2016-05-13 13:51, Mike Bonnet wrote:
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.
Thanks for narrowing this down to a test case.
I was able to reproduce this too on both Windows 7 (sporadically) and
Server 2012 (consistently), but only after updating the "daily"
signatures from 21513 to 21539. Upgrading to 0.99.2 locally did not
help, but disabling bytecode (e.g. --bytecode=no in CLI) seems to be a
Therefore, I suspect its either a bug in LLVM JIT (certainly possible)
or in register handling in Cygwin. Either way, it's going to be some
"fun" to track this down further.
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? :)
There is a bugzilla, but I suspect this will have to be fixed on our end
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple