public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@NexGo.DE>
To: cygwin@cygwin.com
Subject: Re: Please test snapshots
Date: Fri, 17 Aug 2012 09:40:00 -0000	[thread overview]
Message-ID: <loom.20120817T112932-24@post.gmane.org> (raw)
In-Reply-To: <loom.20120809T111739-607@post.gmane.org>

Achim Gratz <Stromeko <at> NexGo.DE> writes:
> With the latest snapshot (2012-08-07), pinging a dead machine (i.e. has a DNS
> entry but doesn't answer) from tcsh in mintty, I can't Ctrl-C ping and have to
> wait until it finally times out.
> 
> #  ping deadbeef
> PING deadbeef (xx.xx.xx.xx): 56 data bytes

This is still happening with the 2012-08-16 19:31:57 UTC snapshot.  The dead
machine cannot be in the same local network or the fail is not happening.  After
Ctrl-C in the tcsh for ping, nothing happens and ps still shows ping as a
running process.  Killing that process ID from another shell kills the shell
ping was started from along with the mintty it was running in.  Trying to attach
to the ping process with gdb recognizes it as "tcsh" rather than ping, which
might explain why killing "ping" actually kills "tcsh".


Regards,
Achim.


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

  parent reply	other threads:[~2012-08-17  9:36 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-06  3:53 Christopher Faylor
2012-08-06  5:14 ` Daniel Colascione
2012-08-06  8:59 ` Achim Gratz
2012-08-08 13:04   ` Achim Gratz
2012-08-09  8:07     ` Achim Gratz
2012-08-06 15:31 ` Filipp Gunbin
2012-08-06 23:27   ` Daniel Colascione
2012-08-07  0:39     ` Daniel Colascione
2012-08-07  0:40       ` Daniel Colascione
2012-08-08 22:17       ` Christopher Faylor
2012-08-09  6:35         ` Daniel Colascione
2012-08-09 12:29         ` Achim Gratz
2012-08-09 14:54           ` Christopher Faylor
2012-08-09 15:06             ` Achim Gratz
2012-08-09 14:59           ` Daniel Colascione
2012-08-10  7:15             ` Achim Gratz
2012-08-10 14:36               ` Christopher Faylor
2012-08-10 18:12                 ` Achim Gratz
2012-08-10 18:34                   ` Christopher Faylor
2012-08-10 19:08                     ` Achim Gratz
2012-08-10 20:24                       ` Christopher Faylor
2012-08-10 20:37                         ` Achim Gratz
2012-08-10 23:31                           ` Christopher Faylor
2012-08-14 13:45                 ` Adam Dinwoodie
2012-08-16 19:01                   ` Christopher Faylor
2012-08-16 19:33                     ` Ken Brown
2012-08-16 19:45                       ` Christopher Faylor
2012-08-16 20:11                         ` Ken Brown
2012-08-17  9:38                     ` Adam Dinwoodie
2012-08-17 14:37                       ` Christopher Faylor
2012-08-17 17:46                         ` Adam Dinwoodie
2012-08-17 18:08                           ` Christopher Faylor
2012-08-17 19:32                         ` Achim Gratz
2012-08-17  9:40           ` Achim Gratz [this message]
2012-08-17 10:47             ` Achim Gratz
2012-08-14 19:23 ` jojelino
2012-08-14 19:41   ` Corinna Vinschen
2012-08-14 19:42     ` Christopher Faylor

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=loom.20120817T112932-24@post.gmane.org \
    --to=stromeko@nexgo.de \
    --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).