public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: core-dump, cygwin64-only in locate in 4.5.11.1
Date: Fri, 18 Apr 2014 22:04:00 -0000	[thread overview]
Message-ID: <5351A157.80106@redhat.com> (raw)
In-Reply-To: <20140415093245.GG3271@calimero.vinschen.de>

[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]

On 04/15/2014 03:32 AM, Corinna Vinschen wrote:
> On Apr 14 14:55, Linda Walsh wrote:
>> I updated 77 cygwin pkgs Mar 19, and since have had
>> problems running
>> 'locate' to completion... it dumps core at what
>> appears to be the end of showing files within
>> 18K of the end of a 22M file.
>>
>>> locate / |& tail -3
>>
>> /Windows/winsxs/x86_wcf-m_svc_mod_svc_perf_reg_31bf3856ad364e35_6.1.7600.16385_none_76916835f088e0d4/_ServiceModelServicePerfCounters.reg
>> /Windows/winsxs/x86_wcf-m_svc_mod_svc_perf_vrg_31bf3856ad364e35_6.1.7600.16385_none_7c54ea6becd48233
>> /Windows/winsxs/x86_wcf-m_svc_mod_svc_perf_vrg_31bf3856ad364e35_6.1.7600.16385_none_7c54ea6becd48233/_ServiSegmentation
>> fault (core dumped)
> 
> I can reproduce it and I *think* I found the problem in the source.
> Alas, what we need is a new findutils package.
> 
> Eric, any chance for an update any time soon?

Does the just-updated 4.5.12-1 fix it, or do I need to look at providing
a more recent git snapshot, since upstream doesn't have any newer release?

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  parent reply	other threads:[~2014-04-18 22:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14 21:56 Linda Walsh
2014-04-15  9:32 ` Corinna Vinschen
2014-04-16  1:22   ` Linda Walsh
2014-04-16  7:54     ` Corinna Vinschen
2014-04-18 22:04   ` Eric Blake [this message]
2014-04-19 11:22     ` Corinna Vinschen

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=5351A157.80106@redhat.com \
    --to=eblake@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).