Fwd: failure notice

Tom Kacvinsky tom.kacvinsky@vectorcast.com
Tue Jan 12 14:14:00 GMT 2016


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



More information about the Cygwin mailing list