DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=oF
	2/K79OaOBLPmzIff8zjry+xJC7fxbHF+pq7seyk/eJTSkyGzj3kQK4YbZkRheVNd
	PQIiLhLaMqu2wPjH+1WzwoFj+t3pKf6/3+k8ve3t5snHk2klKJXsARg8GJGFth8M
	GHDOroSs0WNKqMRBkikdLyDXt1CHvvVJdwLblYcA0=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <CAAEKttwdBJps=CkkQM6NFJa+gsdq1HBD7LOEM6iG0bDrR2rBUQ@mail.gmail.com>
References: <56619fc2.83c1420a.10961.ffffb37fSMTPIN_ADDED_MISSING@mx.google.com>	<CAAEKttw6WETmKSviuX8VfZ-1MKUoZHo=MH=D+QGV8jm6izTQ-A@mail.gmail.com>	<5665A382.2050208@dronecode.org.uk>	<CAAEKttwT123-jh8szrp4u8kxLmXwpuYVgStJKEkwaBk57r6=NQ@mail.gmail.com>	<CAAEKttwYdx-WjjynjNfe=hGBN45moMS6wSRWdb9BMnWbxLKxuA@mail.gmail.com>	<56670A0B.5080707@dronecode.org.uk>	<CAAEKttxPfsi76UGDV2HwdwnqZcZeE5oAax5uC1s4JWu23CC9RQ@mail.gmail.com>	<CAAEKttyO9Q4L1exJn7=Kd5WMbip+vut7YYd4c=hg2W8mCVHXWQ@mail.gmail.com>	<CAAEKttygqO+rqMn1PdYDzNdnZmtArhFL80_M+mdQnCTmk5V8bg@mail.gmail.com>	<CAAEKttzt4HzVPvZSkC_31-XkZeRWPyQzKx0RQABROL1B96j-5w@mail.gmail.com>	<CAAEKttwdBJps=CkkQM6NFJa+gsdq1HBD7LOEM6iG0bDrR2rBUQ@mail.gmail.com>
Date: Tue, 12 Jan 2016 08:58:17 -0500
Message-ID: <CAAEKttwO9T83x6RsR9Ep6327rbYEQL622SYWfqu4ATs0S=1ZSg@mail.gmail.com>
Subject: Re: Fwd: failure notice
From: Tom Kacvinsky <tom.kacvinsky@vectorcast.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8

Bump.  Any word on this?  We would like to solve this before our
customers run into the problem and having any diagnostics tips would
be greatly appreciated.  We are also in a bind because we have run
this by the Qt maintainers and they say they won't fix it.

Thanks,

Tom

On Mon, Jan 4, 2016 at 1:43 PM, Tom Kacvinsky
<tom.kacvinsky@vectorcast.com> wrote:
> On Tue, Dec 22, 2015 at 10:34 AM, Tom Kacvinsky
> <tom.kacvinsky@vectorcast.com> wrote:
>> It turns out we are using the 32 bit version of cygwin, so I am going
>> to try with 64 bit cygwin and the latest possible version and see how
>> I fare.
>
> Happens with both 32 and 64 bit cygwin.  I'm out of ideas.  The
> developer here that I have been working with seems to think this ia
> cygwin bug as this didn't happen in the 1.7 releases, and the version
> of Qt we are using hasn't changed in between the cygwin versions we
> are using.
>
> Any other ideas?  Is there an environment variable or debug option we
> can set to help track this down?

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