public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: Ping crashes
Date: Sat, 27 Oct 2018 16:07:00 -0000	[thread overview]
Message-ID: <022b53a72c3c15fff6d5fb56c3df3134@smtp-cloud8.xs4all.net> (raw)
In-Reply-To: <SN6PR09MB324734F8016EE54FD0DCE436A5F10@SN6PR09MB3247.namprd09.prod.outlook.com>

On Sat, 27 Oct 2018 15:25:50, XXXXX wrote:
> Hello,
> 
> I have a problem with the ping utility on Cygwin: it keeps crashing with se=
> gmentation fault.  I've checked that all my packages (including Cygwin core)
[snip]

> $ ping 192.168.1.1
> Segmentation fault (core dumped)

Confirmed ... That is ..

64-@@ ping 192.168.178.1
Segmentation fault (core dumped)
64-@@

64-@@# ping 192.168.178.1 <==== using an elevated shell:
PING 192.168.178.1 (192.168.178.1): 56 data bytes
64 bytes from 192.168.178.1: icmp_seq=0 ttl=64 time=0.000 ms
64 bytes from 192.168.178.1: icmp_seq=1 ttl=64 time=0.000 ms
64 bytes from 192.168.178.1: icmp_seq=2 ttl=64 time=0.000 ms
64 bytes from 192.168.178.1: icmp_seq=3 ttl=64 time=0.000 ms
64 bytes from 192.168.178.1: icmp_seq=4 ttl=64 time=0.000 ms
64 bytes from 192.168.178.1: icmp_seq=5 ttl=64 time=0.000 ms
64 bytes from 192.168.178.1: icmp_seq=6 ttl=64 time=0.000 ms
--- 192.168.178.1 ping statistics ---
7 packets transmitted, 7 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.000/0.000/0.000/0.000 ms
64-@@#

Regards,
Henri


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

  reply	other threads:[~2018-10-27 16:07 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 [this message]
2018-10-27 16:21 ` Houder
2018-10-29 12:27 ` Takashi Yano
2018-10-29 15:40 ` Corinna Vinschen
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=022b53a72c3c15fff6d5fb56c3df3134@smtp-cloud8.xs4all.net \
    --to=houder@xs4all.nl \
    --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).