From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] clamav 0.99.1-1
Date: Fri, 13 May 2016 22:14:00 -0000 [thread overview]
Message-ID: <0e5a6d56-ce89-8e9c-ae07-48e092927bc7@cygwin.com> (raw)
In-Reply-To: <d165fc48-cf32-6e55-9bfa-d727899dcc76@redhat.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.
Mike,
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
workaround.
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
somewhere.
--
Yaakov
--
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
prev parent reply other threads:[~2016-05-13 22:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 17:35 Yaakov Selkowitz
2016-05-11 14:35 ` Mike Bonnet
2016-05-11 15:18 ` Yaakov Selkowitz
2016-05-11 16:11 ` Mike Bonnet
2016-05-11 16:14 ` Warren Young
2016-05-13 18:51 ` Mike Bonnet
2016-05-13 22:14 ` Yaakov Selkowitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0e5a6d56-ce89-8e9c-ae07-48e092927bc7@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).