From: Andrey Repin <anrdaemon@freemail.ru>
To: Jamie Briggs <jamie.briggs@shaw.ca>, cygwin@cygwin.com
Subject: Re: cygwin 1.7.15-1 - .NET console output locks up mintty
Date: Fri, 22 Jun 2012 10:50:00 -0000 [thread overview]
Message-ID: <31937321.20120622144920@mtu-net.ru> (raw)
In-Reply-To: <20120622022137.GA24472@shaw.ca>
Greetings, Jamie Briggs!
> I have noticed a problem with the â"cygwin: The Unix emulation engine" package,
> version 1.7.15-1. Output from .NET console does not show up, the console
> (mintty) becomes unresponsive and must be killed.
> Reverting back to 1.7.14-2 fixes the problem.
> The problem can be demonstrated using a HelloWorld.cs containing:
> using System;
> public class Program
> {
> static void Main(string[] args)
> {
> Console.WriteLine("Hello");
> }
> }
> compiling with: csc HelloWorld.cs
> and then running: ./HelloWorld.exe
> This results in no output and an unresponsive mintty under 1.7.15-1. If
> "cmd.exe" is ran on top of bash and then HelloWorld is ran there it does the
> same thing. After reverting to 1.7.14-2 everything is working normally again.
> I am building the executables with VS2010 and running on 64bit Windows7. I am
> attaching my cygcheck.out file.
"If you can reproduce this behavior in plain C, we will be able to investigate
the cause. Probably" (c) mailing list.
Your issue, from the look of it, has been discussed already, please look in
the list archive.
--
WBR,
Andrey Repin (anrdaemon@freemail.ru) 22.06.2012, <14:47>
Sorry for my terrible english...
next prev parent reply other threads:[~2012-06-22 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 2:22 Jamie Briggs
2012-06-22 10:50 ` Andrey Repin [this message]
2012-06-22 18:10 ` Jamie Briggs
2012-06-22 21:50 ` Andrey Repin
2012-06-25 13:51 ` James Johnston
2012-06-22 11:46 ` Earnie Boyd
2012-06-22 14:43 ` James Johnston
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=31937321.20120622144920@mtu-net.ru \
--to=anrdaemon@freemail.ru \
--cc=cygwin@cygwin.com \
--cc=jamie.briggs@shaw.ca \
/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).