Mintty 2.2.2: possible hang when breaking (CTRL+C) out of pinging unresponsive host

Mintty 2.2.2: possible hang when breaking (CTRL+C) out of pinging unresponsive host

[Jeff Hansen]

[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]

I have recently installed the latest 32-bit version of Cygwin on my Windows
10 Professional operating system.

When I ping a host, and the ping doesn't reply for a few minutes, I find the
ping hangs when I try to break out of it using CTRL+C.
IT is at this point I have to close the Mintty window completely and re-open
as it is unresponsive.
Any pings to a host that does reply doesn't result in a 'hung ping', as
described here.

My only fix up to this point is to downgrade to a previous installation of
Cygwin that I've had for approx. 5 years now.  That copy has Mintty ver
0.9.9 installed. 

I did attempt to go through the various forums and sites to try to find
other previous reports of this, and while I did find some previous reports
of this happening, I have been unable to find a solution that fixed the
problem I am having.

I try my hardest to not bother you good people. but I am at my wits end at
what to try here.  Any and all suggestions that works towards a solution is
very welcome.


-Jeff


[-- Attachment #2: cygcheck.out --]
[-- Type: application/octet-stream, Size: 13216 bytes --]


Cygwin Configuration Diagnostics
Current System Time: Tue Nov 24 21:02:49 2015

Windows 10 Professional Ver 10.0 Build 10240 

Running under WOW64 on AMD64

Path:	C:\cygwin\usr\local\bin
	C:\cygwin\bin
	C:\ProgramData\Oracle\Java\javapath
	C:\windows\system32
	C:\windows
	C:\windows\System32\Wbem
	C:\windows\System32\WindowsPowerShell\v1.0
	C:\Program Files (x86)\Skype\Phone

Output from C:\cygwin\bin\id.exe
UID: 197609(jeffh)
GID: 197609(jeffh)
197609(jeffh)
405504(High Mandatory Level)
114(Local account and member of Administrators group)
544(Administrators)
545(Users)
4(INTERACTIVE)
66049(CONSOLE LOGON)
11(Authenticated Users)
15(This Organization)
68466(MicrosoftAccount+jeff.hansen@vianet.ca)
113(Local account)
66048(LOCAL)
262180(Cloud Account Authentication)

SysDir: C:\windows\system32
WinDir: C:\windows

USER = 'jeffh'
PWD = '/home/jeffh'
HOME = '/home/jeffh'

USERDOMAIN_ROAMINGPROFILE = 'SURFPRO4-PC'
HOMEPATH = '\Users\jeffh'
APPDATA = 'C:\Users\jeffh\AppData\Roaming'
ProgramW6432 = 'C:\Program Files'
HOSTNAME = 'SURFPRO4-PC'
SHELL = '/bin/bash'
TERM = 'xterm'
PROCESSOR_IDENTIFIER = 'Intel64 Family 6 Model 78 Stepping 3, GenuineIntel'
PROFILEREAD = 'true'
WINDIR = 'C:\windows'
PUBLIC = 'C:\Users\Public'
OLDPWD = '/cygdrive/c/windows/system32'
ORIGINAL_PATH = '/cygdrive/c/ProgramData/Oracle/Java/javapath:/cygdrive/c/windows/system32:/cygdrive/c/windows:/cygdrive/c/windows/System32/Wbem:/cygdrive/c/windows/System32/WindowsPowerShell/v1.0:/cygdrive/c/Program Files (x86)/Skype/Phone'
USERDOMAIN = 'SURFPRO4-PC'
CommonProgramFiles(x86) = 'C:\Program Files (x86)\Common Files'
OS = 'Windows_NT'
ALLUSERSPROFILE = 'C:\ProgramData'
TEMP = '/tmp'
COMMONPROGRAMFILES = 'C:\Program Files (x86)\Common Files'
USERNAME = 'jeffh'
PROCESSOR_LEVEL = '6'
ProgramFiles(x86) = 'C:\Program Files (x86)'
PSModulePath = 'C:\windows\system32\WindowsPowerShell\v1.0\Modules\'
SYSTEMDRIVE = 'C:'
PROCESSOR_ARCHITEW6432 = 'AMD64'
__COMPAT_LAYER = 'Installer'
LANG = 'en_US.UTF-8'
USERPROFILE = 'C:\Users\jeffh'
TZ = 'America/New_York'
PS1 = '\[\e]0;\w\a\]\n\[\e[32m\]\u@\h \[\e[33m\]\w\[\e[0m\]\n\$ '
LOGONSERVER = '\\MicrosoftAccount'
CommonProgramW6432 = 'C:\Program Files\Common Files'
PROCESSOR_ARCHITECTURE = 'x86'
LOCALAPPDATA = 'C:\Users\jeffh\AppData\Local'
ProgramData = 'C:\ProgramData'
EXECIGNORE = '*.dll'
SHLVL = '1'
PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC'
HOMEDRIVE = 'C:'
COMSPEC = 'C:\windows\system32\cmd.exe'
TMP = '/tmp'
SYSTEMROOT = 'C:\windows'
PRINTER = 'Brother MFC-J825DW Printer'
PROCESSOR_REVISION = '4e03'
INFOPATH = '/usr/local/info:/usr/share/info:/usr/info'
PROGRAMFILES = 'C:\Program Files (x86)'
NUMBER_OF_PROCESSORS = '4'
COMPUTERNAME = 'SURFPRO4-PC'
_ = '/usr/bin/cygcheck'

HKEY_CURRENT_USER\SOFTWARE\Cygwin
HKEY_CURRENT_USER\SOFTWARE\Cygwin\Installations
  (default) = '\??\C:\cygwin'
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Installations
  (default) = '\??\C:\cygwin'
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\setup
  (default) = 'C:\cygwin'

obcaseinsensitive set to 1

Cygwin installations found in the registry:
  System: Key: c5e39b7a9d22bafb Path: C:\cygwin
  User:   Key: c5e39b7a9d22bafb Path: C:\cygwin

c:  hd  NTFS    487076Mb  11% CP CS UN PA FC     Windows

C:\cygwin        /          system  binary,auto
C:\cygwin\bin    /usr/bin   system  binary,auto
C:\cygwin\lib    /usr/lib   system  binary,auto
cygdrive prefix  /cygdrive  user    binary,posix=0,auto

Found: C:\cygwin\bin\awk
 -> C:\cygwin\bin\gawk.exe
Found: C:\cygwin\bin\bash.exe
Found: C:\cygwin\bin\cat.exe
Found: C:\cygwin\bin\cp.exe
Not Found: cpp (good!)
Not Found: crontab
Found: C:\cygwin\bin\find.exe
Found: C:\windows\system32\find.exe
Warning: C:\cygwin\bin\find.exe hides C:\windows\system32\find.exe
Not Found: gcc
Not Found: gdb
Found: C:\cygwin\bin\grep.exe
Found: C:\cygwin\bin\kill.exe
Not Found: ld
Found: C:\cygwin\bin\ls.exe
Not Found: make
Found: C:\cygwin\bin\mv.exe
Not Found: patch
Not Found: perl
Found: C:\cygwin\bin\rm.exe
Found: C:\cygwin\bin\sed.exe
Not Found: ssh
Found: C:\cygwin\bin\sh.exe
Found: C:\cygwin\bin\tar.exe
Found: C:\cygwin\bin\test.exe
Found: C:\cygwin\bin\vi.exe
Not Found: vim

   38k 2013/07/23 C:\cygwin\bin\cygargp-0.dll - os=4.0 img=1.0 sys=4.0
                  "cygargp-0.dll" v0.0 ts=2013-07-23 15:35
   14k 2012/05/04 C:\cygwin\bin\cygattr-1.dll - os=4.0 img=1.0 sys=4.0
                  "cygattr-1.dll" v0.0 ts=2012-05-04 12:35
  203k 2015/03/23 C:\cygwin\bin\cygblkid-1.dll - os=4.0 img=1.0 sys=4.0
                  "cygblkid-1.dll" v0.0 ts=2015-03-23 09:55
   62k 2011/05/21 C:\cygwin\bin\cygbz2-1.dll - os=4.0 img=1.0 sys=4.0
                  "cygbz2-1.dll" v0.0 ts=2011-05-21 20:16
 1980k 2015/07/09 C:\cygwin\bin\cygcrypto-1.0.0.dll - os=4.0 img=1.0 sys=4.0
                  "cygcrypto-1.0.0.dll" v0.0 ts=2015-07-09 17:50
   27k 2015/01/02 C:\cygwin\bin\cygffi-6.dll - os=4.0 img=1.0 sys=4.0
                  "cygffi-6.dll" v0.0 ts=2015-01-02 01:11
   60k 2015/10/20 C:\cygwin\bin\cygformw-10.dll - os=4.0 img=1.0 sys=4.0
                  "cygformw-10.dll" v0.0 ts=2015-10-20 17:07
  108k 2015/07/02 C:\cygwin\bin\cyggcc_s-1.dll - os=4.0 img=1.0 sys=4.0
                  "cyggcc_s-1.dll" v0.0 ts=2015-07-02 18:59
   19k 2009/02/26 C:\cygwin\bin\cyggdbm-4.dll - os=4.0 img=1.0 sys=4.0
                  "cyggdbm-4.dll" v0.0 ts=2009-02-26 07:58
    8k 2009/02/26 C:\cygwin\bin\cyggdbm_compat-4.dll - os=4.0 img=1.0 sys=4.0
                  "cyggdbm_compat-4.dll" v0.0 ts=2009-02-26 07:58
  507k 2015/11/07 C:\cygwin\bin\cyggmp-10.dll - os=4.0 img=1.0 sys=4.0
                  "cyggmp-10.dll" v0.0 ts=2015-11-07 18:45
   31k 2015/01/27 C:\cygwin\bin\cyghistory7.dll - os=4.0 img=1.0 sys=4.0
                  "cyghistory7.dll" v0.0 ts=2015-01-27 23:43
 1010k 2015/02/20 C:\cygwin\bin\cygiconv-2.dll - os=4.0 img=1.0 sys=4.0
                  "cygiconv-2.dll" v0.0 ts=2015-02-20 16:52
   41k 2015/09/20 C:\cygwin\bin\cygintl-8.dll - os=4.0 img=1.0 sys=4.0
                  "cygintl-8.dll" v0.0 ts=2015-09-20 20:20
    5k 2015/11/14 C:\cygwin\bin\cyglsa.dll - os=4.0 img=1.0 sys=4.0
                  "cyglsa.dll" v0.0 ts=2015-11-14 11:42
    6k 2015/11/14 C:\cygwin\bin\cyglsa64.dll (not x86 dll)
  159k 2015/11/09 C:\cygwin\bin\cyglzma-5.dll - os=4.0 img=1.0 sys=4.0
                  "cyglzma-5.dll" v0.0 ts=2015-11-09 06:13
  123k 2015/08/12 C:\cygwin\bin\cygmagic-1.dll - os=4.0 img=1.0 sys=4.0
                  "cygmagic-1.dll" v0.0 ts=2015-08-12 20:06
  173k 2015/10/09 C:\cygwin\bin\cygman-2-7-4.dll - os=4.0 img=1.0 sys=4.0
                  "cygman-2-7-4.dll" v0.0 ts=2015-10-09 09:30
   22k 2015/10/09 C:\cygwin\bin\cygmandb-2-7-4.dll - os=4.0 img=1.0 sys=4.0
                  "cygmandb-2-7-4.dll" v0.0 ts=2015-10-09 09:30
   30k 2015/10/20 C:\cygwin\bin\cygmenuw-10.dll - os=4.0 img=1.0 sys=4.0
                  "cygmenuw-10.dll" v0.0 ts=2015-10-20 17:06
  369k 2015/06/30 C:\cygwin\bin\cygmpfr-4.dll - os=4.0 img=1.0 sys=4.0
                  "cygmpfr-4.dll" v0.0 ts=2015-06-30 18:39
   57k 2015/10/20 C:\cygwin\bin\cygncurses++w-10.dll - os=4.0 img=1.0 sys=4.0
                  "cygncurses++w-10.dll" v0.0 ts=2015-10-20 17:12
  327k 2015/10/20 C:\cygwin\bin\cygncursesw-10.dll - os=4.0 img=1.0 sys=4.0
                  "cygncursesw-10.dll" v0.0 ts=2015-10-20 17:05
  326k 2015/06/01 C:\cygwin\bin\cygp11-kit-0.dll - os=4.0 img=1.0 sys=4.0
                  "cygp11-kit-0.dll" v0.0 ts=2015-06-01 20:17
   15k 2015/10/20 C:\cygwin\bin\cygpanelw-10.dll - os=4.0 img=1.0 sys=4.0
                  "cygpanelw-10.dll" v0.0 ts=2015-10-20 17:06
  458k 2015/08/11 C:\cygwin\bin\cygpcre-1.dll - os=4.0 img=1.0 sys=4.0
                  "cygpcre-1.dll" v0.0 ts=2015-08-11 18:40
   41k 2015/04/09 C:\cygwin\bin\cygpipeline-1.dll - os=4.0 img=1.0 sys=4.0
                  "cygpipeline-1.dll" v0.0 ts=2015-04-09 20:58
   41k 2013/10/21 C:\cygwin\bin\cygpopt-0.dll - os=4.0 img=1.0 sys=4.0
                  "cygpopt-0.dll" v0.0 ts=2013-10-21 21:52
  208k 2015/01/27 C:\cygwin\bin\cygreadline7.dll - os=4.0 img=1.0 sys=4.0
                  "cygreadline7.dll" v0.0 ts=2015-01-27 23:43
   98k 2015/03/23 C:\cygwin\bin\cygsmartcols-1.dll - os=4.0 img=1.0 sys=4.0
                  "cygsmartcols-1.dll" v0.0 ts=2015-03-23 09:55
  446k 2015/07/09 C:\cygwin\bin\cygssl-1.0.0.dll - os=4.0 img=1.0 sys=4.0
                  "cygssl-1.0.0.dll" v0.0 ts=2015-07-09 17:50
  944k 2015/07/02 C:\cygwin\bin\cygstdc++-6.dll - os=4.0 img=1.0 sys=4.0
                  "cygstdc++-6.dll" v0.0 ts=2015-07-02 19:14
   69k 2015/08/28 C:\cygwin\bin\cygtasn1-6.dll - os=4.0 img=1.0 sys=4.0
                  "cygtasn1-6.dll" v0.0 ts=2015-08-28 09:48
   55k 2015/10/20 C:\cygwin\bin\cygticw-10.dll - os=4.0 img=1.0 sys=4.0
                  "cygticw-10.dll" v0.0 ts=2015-10-20 17:05
   16k 2015/03/23 C:\cygwin\bin\cyguuid-1.dll - os=4.0 img=1.0 sys=4.0
                  "cyguuid-1.dll" v0.0 ts=2015-03-23 09:55
   83k 2014/11/19 C:\cygwin\bin\cygz.dll - os=4.0 img=1.0 sys=4.0
                  "cygz.dll" v0.0 ts=2014-11-19 22:57
 3407k 2015/11/14 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
                  "cygwin1.dll" v0.0 ts=2015-11-14 11:42
    Cygwin DLL version info:
        DLL version: 2.3.1
        DLL epoch: 19
        DLL old termios: 5
        DLL malloc env: 28
        Cygwin conv: 181
        API major: 0
        API minor: 291
        Shared data: 5
        DLL identifier: cygwin1
        Mount registry: 3
        Cygwin registry name: Cygwin
        Installations name: Installations
        Cygdrive default prefix: 
        Build date: 
        Shared id: cygwin1S5


Can't find the cygrunsrv utility, skipping services check.


Cygwin Package Information
Last downloaded files to: C:\Users\jeffh\Downloads\cygwin-install-dir
Last downloaded files from: http://mirror.csclub.uwaterloo.ca/cygwin/

Package              Version            Status
_autorebase          001002-1           OK
_update-info-dir     01460-1            OK
alternatives         1.3.30c-10         OK
base-cygwin          3.8-1              OK
base-files           4.2-4              OK
bash                 4.3.42-4           OK
bzip2                1.0.6-2            OK
ca-certificates      2.5-1              OK
coreutils            8.24-3             OK
cygutils             1.4.15-1           OK
cygwin               2.3.1-1            OK
dash                 0.5.8-3            OK
editrights           1.03-1             OK
file                 5.24-1             OK
findutils            4.5.12-1           OK
gawk                 4.1.3-1            OK
getent               2.18.90-4          OK
grep                 2.21-2             OK
groff                1.22.3-1           OK
gzip                 1.6-1              OK
hostname             3.13-1             OK
info                 6.0-1              OK
ipc-utils            1.0-1              OK
iperf                2.0.5-1            OK
less                 481-1              OK
libargp              20110921-2         OK
libattr1             2.4.46-1           OK
libblkid1            2.25.2-2           OK
libbz2_1             1.0.6-2            OK
libffi6              3.2.1-1            OK
libgcc1              4.9.3-1            OK
libgdbm4             1.8.3-20           OK
libgmp10             6.1.0-1            OK
libiconv             1.14-3             OK
libiconv2            1.14-3             OK
libintl8             0.19.5.1-2         OK
liblzma5             5.2.2-1            OK
libmpfr4             3.1.3-1            OK
libncursesw10        6.0-1.20151017     OK
libopenssl100        1.0.2d-1           OK
libp11-kit0          0.22.1-1           OK
libpcre1             8.37-2             OK
libpipeline1         1.4.0-1            OK
libreadline7         6.3.8-1            OK
libsmartcols1        2.25.2-2           OK
libstdc++6           4.9.3-1            OK
libtasn1_6           4.5-1              OK
libuuid1             2.25.2-2           OK
login                1.11-1             OK
lynx                 2.8.7-1            OK
man-db               2.7.4-1            OK
mintty               2.2.2-0            OK
nano                 2.4.1-1            OK
openssl              1.0.2d-1           OK
p11-kit              0.22.1-1           OK
p11-kit-trust        0.22.1-1           OK
ping                 1.0.2-1            OK
popt                 1.16-1             OK
rebase               4.4.1-1            OK
run                  1.3.4-2            OK
sed                  4.2.2-3            OK
tar                  1.28-1             OK
terminfo             6.0-1.20151017     OK
tzcode               2015g-1            OK
util-linux           2.25.2-2           OK
vim-minimal          7.4.891-1          OK
which                2.20-2             OK
xz                   5.2.2-1            OK
zlib0                1.2.8-3            OK
Use -h to see help about each section


[-- Attachment #3: Type: text/plain, Size: 218 bytes --]

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

Re: Mintty 2.2.2: possible hang when breaking (CTRL+C) out of pinging unresponsive host

[Marco Atzeri]

On 24/11/2015 22:48, Jeff Hansen wrote:
> I have recently installed the latest 32-bit version of Cygwin on my Windows
> 10 Professional operating system.
>
> When I ping a host, and the ping doesn't reply for a few minutes, I find the
> ping hangs when I try to break out of it using CTRL+C.
> IT is at this point I have to close the Mintty window completely and re-open
> as it is unresponsive.
> Any pings to a host that does reply doesn't result in a 'hung ping', as
> described here.
>
> My only fix up to this point is to downgrade to a previous installation of
> Cygwin that I've had for approx. 5 years now.  That copy has Mintty ver
> 0.9.9 installed.
>
> I did attempt to go through the various forums and sites to try to find
> other previous reports of this, and while I did find some previous reports
> of this happening, I have been unable to find a solution that fixed the
> problem I am having.
>
> I try my hardest to not bother you good people. but I am at my wits end at
> what to try here.  Any and all suggestions that works towards a solution is
> very welcome.
>
>
> -Jeff
>

the problem is also present on 64 bit.
As ping on windows console is reacting at CTRL+C
I assume it is an interaction with mintty.

As workaround you should be able to kill ping
with task manager without killing mintty.




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

Re: Mintty 2.2.2: possible hang when breaking (CTRL+C) out of pinging unresponsive host

[Thomas Wolff]

Am 24.11.2015 um 23:29 schrieb Marco Atzeri:
>
> On 24/11/2015 22:48, Jeff Hansen wrote:
>> ...
>> When I ping a host, and the ping doesn't reply for a few minutes, I 
>> find the
>> ping hangs when I try to break out of it using CTRL+C.
>> IT is at this point I have to close the Mintty window completely and 
>> re-open
>> as it is unresponsive.
>> Any pings to a host that does reply doesn't result in a 'hung ping', as
>> described here.
>> ...
>>
>> I try my hardest to not bother you good people. but I am at my wits 
>> end at what to try here.
No worries. That's what this list is for.
>> Any and all suggestions that works towards a solution is
>> very welcome.
> ...
> I assume it is an interaction with mintty.
Many problems of that kind attributed to mintty are actually problems 
with cygwin or especially pty.
Please test also with another terminal (xterm, rxvt, ...).
Also some more details could be helpful as I cannot reproduce the issue 
(output of `type ping`, actual host pinged).
------
Thomas

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

Re: Mintty 2.2.2: possible hang when breaking (CTRL+C) out of pinging unresponsive host

[Marco Atzeri]

On 25/11/2015 08:06, Thomas Wolff wrote:
> Am 24.11.2015 um 23:29 schrieb Marco Atzeri:
>>

>> ...
>> I assume it is an interaction with mintty.
> Many problems of that kind attributed to mintty are actually problems
> with cygwin or especially pty.
> Please test also with another terminal (xterm, rxvt, ...).
> Also some more details could be helpful as I cannot reproduce the issue
> (output of `type ping`, actual host pinged).
> ------
> Thomas

you are right is not a mintty only issue.
Same happens in xterm


$ which ping
/usr/bin/ping

$ ping 2.2.2.2
PING 2.2.2.2 (2.2.2.2): 56 data bytes

It sticks here forever, CTRL+C ineffective.
Process Explorer or Task Manager are needed to kill the process.
Also kill -9 PID is ineffective

On the old cygwin.bat (aka windows cmd)
CTRL+C is effective

  64 $ ping 2.2.2.2
PING 2.2.2.2 (2.2.2.2): 56 data bytes

----2.2.2.2 PING Statistics----
2 packets transmitted, 0 packets received, 100.0% packet loss


Regards
Marco

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

Re: Mintty 2.2.2: possible hang when breaking (CTRL+C) out of pinging unresponsive host

[Jim Reisert AD1C]

On Wed, Nov 25, 2015 at 4:03 AM, Marco Atzeri wrote:

> you are right is not a mintty only issue.
> Same happens in xterm
>
>
> $ which ping
> /usr/bin/ping
>
> $ ping 2.2.2.2
> PING 2.2.2.2 (2.2.2.2): 56 data bytes
>
> It sticks here forever, CTRL+C ineffective.

Worked fine for me using Cygwin64 and Cygwin build 2.4.0(0.292/5/3)

[LTDENA-REISERT:~] $ ping 2.2.2.2

Pinging 2.2.2.2 with 32 bytes of data:

(type CTRL-C here)

[LTDENA-REISERT:~] $


-- 
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us

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

Re: Mintty 2.2.2: possible hang when breaking (CTRL+C) out of pinging unresponsive host

[Thomas Wolff]

Am 25.11.2015 um 19:51 schrieb Jim Reisert AD1C:
> On Wed, Nov 25, 2015 at 4:03 AM, Marco Atzeri wrote:
>
>> you are right is not a mintty only issue.
>> Same happens in xterm
>>
>>
>> $ which ping
>> /usr/bin/ping
>>
>> $ ping 2.2.2.2
>> PING 2.2.2.2 (2.2.2.2): 56 data bytes
>>
>> It sticks here forever, CTRL+C ineffective.
> Worked fine for me using Cygwin64 and Cygwin build 2.4.0(0.292/5/3)
>
> [LTDENA-REISERT:~] $ ping 2.2.2.2
>
> Pinging 2.2.2.2 with 32 bytes of data:
>
> (type CTRL-C here)
>
> [LTDENA-REISERT:~] $
Please note the difference and provide the necessary information (`which 
ping`):
> PING 2.2.2.2 (2.2.2.2): 56 data bytes
> Pinging 2.2.2.2 with 32 bytes of data: 
------
Thomas

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

Re: Mintty 2.2.2: possible hang when breaking (CTRL+C) out of pinging unresponsive host

[Jim Reisert AD1C]

[LTDENA-REISERT:~] $ which ping
/usr/bin/ping

[LTDENA-REISERT:~] $ ls -l `which ping`
-rwxr-xr-x 1 reisert Domain Users 13824 May  3  2014 /usr/bin/ping

-- 
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us

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

Re: Mintty 2.2.2: possible hang when breaking (CTRL+C) out of pinging unresponsive host

[Andrey Repin]

Greetings, Jim Reisert AD1C!

> [LTDENA-REISERT:~] $ which ping
> /usr/bin/ping

> [LTDENA-REISERT:~] $ ls -l `which ping`
> -rwxr-xr-x 1 reisert Domain Users 13824 May  3  2014 /usr/bin/ping

Well, try again with native ping.


-- 
With best regards,
Andrey Repin
Wednesday, November 25, 2015 23:22:38

Sorry for my terrible english...


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

64bit cygwin 2.4.0-0.4 hangs when pinging unresponsive host

[Marco Atzeri]

On 25/11/2015 12:03, Marco Atzeri wrote:
> On 25/11/2015 08:06, Thomas Wolff wrote:
>> Am 24.11.2015 um 23:29 schrieb Marco Atzeri:
>>>
>
>>> ...
>>> I assume it is an interaction with mintty.
>> Many problems of that kind attributed to mintty are actually problems
>> with cygwin or especially pty.
>> Please test also with another terminal (xterm, rxvt, ...).
>> Also some more details could be helpful as I cannot reproduce the issue
>> (output of `type ping`, actual host pinged).
>> ------
>> Thomas
>
> you are right is not a mintty only issue.
> Same happens in xterm
>
>
> $ which ping
> /usr/bin/ping
>
> $ ping 2.2.2.2
> PING 2.2.2.2 (2.2.2.2): 56 data bytes
>
> It sticks here forever, CTRL+C ineffective.
> Process Explorer or Task Manager are needed to kill the process.
> Also kill -9 PID is ineffective
>
> On the old cygwin.bat (aka windows cmd)
> CTRL+C is effective
>
>   64 $ ping 2.2.2.2
> PING 2.2.2.2 (2.2.2.2): 56 data bytes
>
> ----2.2.2.2 PING Statistics----
> 2 packets transmitted, 0 packets received, 100.0% packet loss


the problem seems restricted to the 64bit test version of cygwin.

$ uname -svm
CYGWIN_NT-6.1 2015-11-21 16:59 x86_64

The issue is not present on 2.3.1

$ ping 2.2.2.2
PING 2.2.2.2 (2.2.2.2): 56 data bytes

----2.2.2.2 PING Statistics----
2 packets transmitted, 0 packets received, 100.0% packet loss

$ uname -srm
CYGWIN_NT-6.1 2.3.1(0.291/5/3) x86_64


And the 32 bit version is not impacted

$ ping 2.2.2.2
PING 2.2.2.2 (2.2.2.2): 56 data bytes

----2.2.2.2 PING Statistics----
2 packets transmitted, 0 packets received, 100.0% packet loss

$ uname -srm
CYGWIN_NT-6.1-WOW 2.4.0(0.292/5/3) i686


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

Re: Mintty 2.2.2: possible hang when breaking (CTRL+C) out of pinging unresponsive host

[Marco Atzeri]

On 25/11/2015 20:52, Jim Reisert AD1C wrote:
> [LTDENA-REISERT:~] $ which ping
> /usr/bin/ping
>
> [LTDENA-REISERT:~] $ ls -l `which ping`
> -rwxr-xr-x 1 reisert Domain Users 13824 May  3  2014 /usr/bin/ping
>

you have an alias somewhere

$ /cygdrive/c/windows/System32/ping 2.2.2.2

Pinging 2.2.2.2 with 32 bytes of data:

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

Re: Mintty 2.2.2: possible hang when breaking (CTRL+C) out of pinging unresponsive host

[Ken Brown]

On 11/25/2015 4:03 PM, Marco Atzeri wrote:
> On 25/11/2015 20:52, Jim Reisert AD1C wrote:
>> [LTDENA-REISERT:~] $ which ping
>> /usr/bin/ping
>>
>> [LTDENA-REISERT:~] $ ls -l `which ping`
>> -rwxr-xr-x 1 reisert Domain Users 13824 May  3  2014 /usr/bin/ping
>>
>
> you have an alias somewhere

Not necessarily.  He might have the Cygwin ping package installed.

Ken


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

Re: Mintty 2.2.2: possible hang when breaking (CTRL+C) out of pinging unresponsive host

[Thomas Wolff]

Am 25.11.2015 um 23:44 schrieb Ken Brown:
> On 11/25/2015 4:03 PM, Marco Atzeri wrote:
>> On 25/11/2015 20:52, Jim Reisert AD1C wrote:
>>> [LTDENA-REISERT:~] $ which ping
>>> /usr/bin/ping
>>>
>>> [LTDENA-REISERT:~] $ ls -l `which ping`
>>> -rwxr-xr-x 1 reisert Domain Users 13824 May  3  2014 /usr/bin/ping
>>>
>>
>> you have an alias somewhere
>
> Not necessarily.  He might have the Cygwin ping package installed.
>
> Ken
The point is that his ping is likely to be the Windows ping, judging by 
its output format, despite the output of `which` which may be false. It 
is better to use `type`.

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

Re: 64bit cygwin 2.4.0-0.4 hangs when pinging unresponsive host

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1882 bytes --]

On Nov 25 22:01, Marco Atzeri wrote:
> 
> 
> On 25/11/2015 12:03, Marco Atzeri wrote:
> >On 25/11/2015 08:06, Thomas Wolff wrote:
> >>Am 24.11.2015 um 23:29 schrieb Marco Atzeri:
> >>>
> >
> >>>...
> >>>I assume it is an interaction with mintty.
> >>Many problems of that kind attributed to mintty are actually problems
> >>with cygwin or especially pty.
> >>Please test also with another terminal (xterm, rxvt, ...).
> >>Also some more details could be helpful as I cannot reproduce the issue
> >>(output of `type ping`, actual host pinged).
> >>------
> >>Thomas
> >
> >you are right is not a mintty only issue.
> >Same happens in xterm
> >
> >
> >$ which ping
> >/usr/bin/ping
> >
> >$ ping 2.2.2.2
> >PING 2.2.2.2 (2.2.2.2): 56 data bytes
> >
> >It sticks here forever, CTRL+C ineffective.
> >Process Explorer or Task Manager are needed to kill the process.
> >Also kill -9 PID is ineffective
> >
> >On the old cygwin.bat (aka windows cmd)
> >CTRL+C is effective
> >
> >  64 $ ping 2.2.2.2
> >PING 2.2.2.2 (2.2.2.2): 56 data bytes
> >
> >----2.2.2.2 PING Statistics----
> >2 packets transmitted, 0 packets received, 100.0% packet loss
> 
> 
> the problem seems restricted to the 64bit test version of cygwin.

I think this is pure coincidence.  After some hours debugging this
problem it seems it's a race condition, architecture-independent and
present since quite a while in Cygwin.  In case of ping the race leads
to a blocking socket function missing a signal arrived, thus the
signal is never handled.  This in turn blocks the next signal from being
delivered.

I have a potential fix, but I have to test it a bit.  The signal code
is pretty complicated...


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: 64bit cygwin 2.4.0-0.4 hangs when pinging unresponsive host

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 2272 bytes --]

On Nov 26 21:15, Corinna Vinschen wrote:
> On Nov 25 22:01, Marco Atzeri wrote:
> > 
> > 
> > On 25/11/2015 12:03, Marco Atzeri wrote:
> > >On 25/11/2015 08:06, Thomas Wolff wrote:
> > >>Am 24.11.2015 um 23:29 schrieb Marco Atzeri:
> > >>>
> > >
> > >>>...
> > >>>I assume it is an interaction with mintty.
> > >>Many problems of that kind attributed to mintty are actually problems
> > >>with cygwin or especially pty.
> > >>Please test also with another terminal (xterm, rxvt, ...).
> > >>Also some more details could be helpful as I cannot reproduce the issue
> > >>(output of `type ping`, actual host pinged).
> > >>------
> > >>Thomas
> > >
> > >you are right is not a mintty only issue.
> > >Same happens in xterm
> > >
> > >
> > >$ which ping
> > >/usr/bin/ping
> > >
> > >$ ping 2.2.2.2
> > >PING 2.2.2.2 (2.2.2.2): 56 data bytes
> > >
> > >It sticks here forever, CTRL+C ineffective.
> > >Process Explorer or Task Manager are needed to kill the process.
> > >Also kill -9 PID is ineffective
> > >
> > >On the old cygwin.bat (aka windows cmd)
> > >CTRL+C is effective
> > >
> > >  64 $ ping 2.2.2.2
> > >PING 2.2.2.2 (2.2.2.2): 56 data bytes
> > >
> > >----2.2.2.2 PING Statistics----
> > >2 packets transmitted, 0 packets received, 100.0% packet loss
> > 
> > 
> > the problem seems restricted to the 64bit test version of cygwin.
> 
> I think this is pure coincidence.  After some hours debugging this
> problem it seems it's a race condition, architecture-independent and
> present since quite a while in Cygwin.  In case of ping the race leads
> to a blocking socket function missing a signal arrived, thus the
> signal is never handled.  This in turn blocks the next signal from being
> delivered.
> 
> I have a potential fix, but I have to test it a bit.  The signal code
> is pretty complicated...

I created a new developer snapshot (https://cygwin.com/snapshots/) and
I'm just about writing the release message for the next test release
2.4.0-0.5 which both contain a patch for this problem.  Please give
any of them a try.


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

Re: 64bit cygwin 2.4.0-0.4 hangs when pinging unresponsive host

[Marco Atzeri]

On 27/11/2015 16:07, Corinna Vinschen wrote:
>>>>   64 $ ping 2.2.2.2
>>>> PING 2.2.2.2 (2.2.2.2): 56 data bytes
>>>>
>>>> ----2.2.2.2 PING Statistics----
>>>> 2 packets transmitted, 0 packets received, 100.0% packet loss
>>>
>>>
>>> the problem seems restricted to the 64bit test version of cygwin.
>>
>> I think this is pure coincidence.  After some hours debugging this
>> problem it seems it's a race condition, architecture-independent and
>> present since quite a while in Cygwin.  In case of ping the race leads
>> to a blocking socket function missing a signal arrived, thus the
>> signal is never handled.  This in turn blocks the next signal from being
>> delivered.
>>
>> I have a potential fix, but I have to test it a bit.  The signal code
>> is pretty complicated...
>
> I created a new developer snapshot (https://cygwin.com/snapshots/) and
> I'm just about writing the release message for the next test release
> 2.4.0-0.5 which both contain a patch for this problem.  Please give
> any of them a try.
>
>
> Thanks,
> Corinna
>


It works fine for me
Regards
Marco

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

Re: 64bit cygwin 2.4.0-0.4 hangs when pinging unresponsive host

[Corinna Vinschen]

[-- Attachment #1: Type: text/plain, Size: 1387 bytes --]

On Nov 27 16:47, Marco Atzeri wrote:
> On 27/11/2015 16:07, Corinna Vinschen wrote:
> >>>>  64 $ ping 2.2.2.2
> >>>>PING 2.2.2.2 (2.2.2.2): 56 data bytes
> >>>>
> >>>>----2.2.2.2 PING Statistics----
> >>>>2 packets transmitted, 0 packets received, 100.0% packet loss
> >>>
> >>>
> >>>the problem seems restricted to the 64bit test version of cygwin.
> >>
> >>I think this is pure coincidence.  After some hours debugging this
> >>problem it seems it's a race condition, architecture-independent and
> >>present since quite a while in Cygwin.  In case of ping the race leads
> >>to a blocking socket function missing a signal arrived, thus the
> >>signal is never handled.  This in turn blocks the next signal from being
> >>delivered.
> >>
> >>I have a potential fix, but I have to test it a bit.  The signal code
> >>is pretty complicated...
> >
> >I created a new developer snapshot (https://cygwin.com/snapshots/) and
> >I'm just about writing the release message for the next test release
> >2.4.0-0.5 which both contain a patch for this problem.  Please give
> >any of them a try.
> >
> >
> >Thanks,
> >Corinna
> >
> 
> 
> It works fine for me

Good start.  Thanks for your feedback.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]