From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: CppUTest generated executables hangs after cygwin auto-update
Date: Thu, 23 May 2013 15:13:00 -0000 [thread overview]
Message-ID: <20130523151305.GJ22259@calimero.vinschen.de> (raw)
In-Reply-To: <20130523150319.GB7647@ednor.casa.cgf.cx>
On May 23 11:03, Christopher Faylor wrote:
> On Thu, May 23, 2013 at 02:29:28PM +0200, Corinna Vinschen wrote:
> >On May 23 13:58, Ralf Glaser, track IT wrote:
> >> Corinna,
> >>
> >> when i replace the original cygwin DLL (which was installed with
> >> cygwin-1.7.17) with the snapshot from 2012-11-23 the problem is
> >> already there.
> >> Maybe just replacing the DLL is not what you had in mind?
> >
> >That was all, yes. Did you test the 2012-10-16 DLL, too, by any chance?
>
> As long as we're testing snapshots, how about testing the latest one?
See the last paragraph in my latest reply.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
--
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
next prev parent reply other threads:[~2013-05-23 15:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 11:58 Ralf Glaser, track IT
2013-05-23 12:29 ` Corinna Vinschen
2013-05-23 15:03 ` Christopher Faylor
2013-05-23 15:13 ` Corinna Vinschen [this message]
2013-05-24 9:03 ` Ralf Glaser, track IT
2013-05-24 10:38 ` Corinna Vinschen
2013-05-24 11:39 ` Ralf Glaser, track IT
2013-05-24 12:33 ` Corinna Vinschen
2013-05-24 15:08 ` Ralf Glaser, track IT
2013-05-24 15:11 ` Ralf Glaser, track IT
2013-05-24 17:13 ` Ralf Glaser, track IT
2013-05-24 21:37 ` Corinna Vinschen
2013-06-04 11:16 ` Ralf Glaser, track IT
2013-06-04 11:32 ` Corinna Vinschen
-- strict thread matches above, loose matches on Subject: below --
2013-05-23 9:13 Ralf Glaser, track IT
2013-05-23 9:34 ` 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=20130523151305.GJ22259@calimero.vinschen.de \
--to=corinna-cygwin@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).