From: "Roger K. Wells" <ROGER.K.WELLS@saic.com>
To: cygwin@cygwin.com
Subject: Re: CTRL+C is not working with java on latest cygwin 1.7.15
Date: Thu, 02 Aug 2012 17:31:00 -0000 [thread overview]
Message-ID: <501AB915.5050106@saic.com> (raw)
In-Reply-To: <34147841.post@talk.nabble.com>
On 07/11/2012 04:07 PM, saltnlight5 wrote:
> Thanks for the reply "K Stahl", but it didn't work for me. I ran the same
> Test, then press CTRL+C. But the cygwin terminal did nothing. It did not
> stop the java process, and it did not print any thing further. I must
> manually terminate the process by going into Windows TaskManager.
>
> Again, here is my cygwin version:
> $ uname -srv
> CYGWIN_NT-5.1 1.7.15(0.260/5/3) 2012-05-09 10:25
>
> Am I on the latest version as you said? Did I miss any other config?
>
> Thanks
> Zemian
>
>
> saltnlight5 wrote:
>> I do have the latest cygwin install. In fact I re-installed just today and
>> it's still not working.
>>
>> I printed the full version in my previous email. Was that not the lastest
>> cygwin version?
>>
>>
>> K Stahl wrote:
>>> Just tested with this against the latest release version (1.7.15) and
>>> everything works as expected.
>>>
>>> Example:
>>> public final class Test {
>>> public static void main(String[] args) {
>>> System.out.println("This shall hang until CTRL-C is pressed...");
>>> for (;;);
>>> }
>>> }
>>>
>>> javac -cp . Test.java
>>> java -cp . Test
>>>
>>> Press CTRL-C and you are returned to the terminal.
>>>
>>> --
>>> 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
>>>
>>>
>>>
>>
>
> -----
> ----
> Zemian Deng
This is still a problem.
CYGWIN_NT-6.1 rwells-w7 1.7.16(0.262/5/3) 2012-07-20 22:55 i686 Cygwin
We have been developing CLI applications for close to 20 years and have
never had a
problem with the cygwin bash shell failing to pass Ctrl-C signals to the
application until now.
Luckily the cmd.exe still does.
Let me know if it something that I can help track down. Glad to help if
possible.
--
Roger Wells, P.E.
SAIC
221 Third St
Newport, RI 02840
401-847-4210 (voice)
401-849-1585 (fax)
roger.k.wells@saic.com
--
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:[~2012-08-02 17:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 18:47 saltnlight5
2012-07-11 19:18 ` K Stahl
[not found] ` <1355306723156-63181.post@n5.nabble.com>
2012-07-11 19:55 ` saltnlight5
2012-07-11 20:06 ` K Stahl
2012-07-11 20:07 ` saltnlight5
2012-07-11 20:17 ` K Stahl
2012-07-11 20:26 ` saltnlight5
2012-07-11 20:34 ` K Stahl
2012-07-11 20:37 ` K Stahl
2012-07-12 1:40 ` Earnie Boyd
2012-07-12 13:02 ` saltnlight5
2012-07-12 13:23 ` K Stahl
2012-07-12 15:39 ` Earnie Boyd
2012-07-12 20:13 ` James Johnston
2012-07-12 21:39 ` saltnlight5
2012-08-02 17:31 ` Roger K. Wells [this message]
2012-12-12 10:05 ` erik56d
2012-12-12 14:06 ` Aaron Schneider
2012-12-12 17:26 ` erik56d
2012-07-12 14:24 ` Aaron Schneider
2012-07-12 21:57 ` saltnlight5
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=501AB915.5050106@saic.com \
--to=roger.k.wells@saic.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).