On Oct 27 15:25, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote:
> Hello,
> 
> I have a problem with the ping utility on Cygwin: it keeps crashing with segmentation fault.  I've checked that all my packages (including Cygwin core)
> are up to date.  What am I missing?  At any rate, I guess it should not have crashed ungracefully if it needs something it doesn't have (like a permission); instead, if should have said so and bail out with an error exit code rather than a stackdump (attached).
> 
> Thanks,
> Anton Lavrentiev
> 
> P.S. ping -h works; ping with any IP address -- crashes
> 
> $ ping 192.168.1.1
> Segmentation fault (core dumped)
> 
> $ cat ping.exe.stackdump
> Exception: STATUS_ACCESS_VIOLATION at rip=001800579D7
> rax=0000000180322500 rbx=000000018031FCF8 rcx=0000000000000000
> rdx=0000000000000003 rsi=0000000000000003 rdi=0000000000000003
> r8 =000000000000001F r9 =00000000000000FE r10=0000000180204E70
> r11=00000000FFFFC892 r12=0000000000000000 r13=0000000000000003
> r14=0000000000000001 r15=0000000000000000
> rbp=0000000000000018 rsp=00000000FFFFCAA0
> program=C:\cygwin64\bin\ping.exe, pid 6496, thread main
> cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B

I just pushed a patch supposed to fix this issue.  The bug is actually
worse and potentially affects more than just ping.  Every time a socket,
socketpair, or accept call fails for some reason, there's a potential
SEGV.  Oh, boy, oh boy.

I've just uploaded developer snapshots to https://cygwin.com/snapshots/
Please test.

I think this qualifies for a 2.11.2 release pretty soon...


Thanks,
Corinna

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