public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mike Bonnet <mikeb@redhat.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] clamav 0.99.1-1
Date: Wed, 11 May 2016 16:11:00 -0000	[thread overview]
Message-ID: <360d98a0-8e44-e816-ea44-d87a2e2655a4@redhat.com> (raw)
In-Reply-To: <4f86f77b-e2cb-b654-760b-499623dd61a1@cygwin.com>

On 5/11/16 8:18 AM, Yaakov Selkowitz wrote:
> On 2016-05-11 09:35, Mike Bonnet wrote:
>> I'm seeing segfaults with this version when recursively scanning large
>> directories. Running Cygwin x86_64 on Windows Server 2012.
>
> But not with 0.99?  Have you been able to reproduce this on any other
> systems?

Only saw it with 0.99.1. Yes, saw it on several systems, all running 0.99.1.

>> In the past
>
> When?

This was several years ago.

>> this happened when some 32-bit files were in the source tree
>> when the 64-bit version was built. It's possible this happened again.
>
> Extremely unlikely.  cygport makes 32-bit and 64-bit builds in their own
> directories.
>
>> 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.


--
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

  reply	other threads:[~2016-05-11 16:11 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 [this message]
2016-05-11 16:14       ` Warren Young
2016-05-13 18:51         ` Mike Bonnet
2016-05-13 22:14           ` Yaakov Selkowitz

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=360d98a0-8e44-e816-ea44-d87a2e2655a4@redhat.com \
    --to=mikeb@redhat.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).