public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Ping crashes
Date: Mon, 29 Oct 2018 15:40:00 -0000	[thread overview]
Message-ID: <20181029154043.GS3310@calimero.vinschen.de> (raw)
In-Reply-To: <SN6PR09MB324734F8016EE54FD0DCE436A5F10@SN6PR09MB3247.namprd09.prod.outlook.com>

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

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2018-10-29 15:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-27 15:26 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2018-10-27 16:07 ` Houder
2018-10-27 16:21 ` Houder
2018-10-29 12:27 ` Takashi Yano
2018-10-29 15:40 ` Corinna Vinschen [this message]
2018-10-29 16:39   ` Houder
2018-10-30  9:09     ` Corinna Vinschen
2018-10-29 21:05   ` Andrey Repin
2018-10-30  9:09     ` Corinna Vinschen

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=20181029154043.GS3310@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.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).