Re: Ping crashes

2018-10-30 Thread Corinna Vinschen
On Oct 29 23:59, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
> 
> > 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 wonder if that explains occasional curl coredumps?

Maybe, yeah.

> 
> > 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...
> 
> Thank you.

Pushing a test release in a few mins...


Thanks,
Corinna

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


signature.asc
Description: PGP signature


Re: Ping crashes

2018-10-30 Thread Corinna Vinschen
On Oct 29 17:39, Houder wrote:
> On Mon, 29 Oct 2018 16:40:43, Corinna Vinschen  wrote:
> > 
> > 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 co=
> [snip]
> 
> > 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,
> 
> Tested for ping on both x86_64 and x86. Solved.

Thanks for testing, but we need more testing for normal network
operations, too.  I'm going to push out a test release in a few
mins.


Thanks,
Corinna

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


signature.asc
Description: PGP signature


Re: Ping crashes

2018-10-29 Thread Andrey Repin
Greetings, Corinna Vinschen!

> 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 wonder if that explains occasional curl coredumps?

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

Thank you.


-- 
With best regards,
Andrey Repin
Monday, October 29, 2018 23:56:55

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



Re: Ping crashes

2018-10-29 Thread Houder
On Mon, 29 Oct 2018 16:40:43, Corinna Vinschen  wrote:
> 
> 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 co=
[snip]

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

Tested for ping on both x86_64 and x86. Solved.

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



Re: Ping crashes

2018-10-29 Thread Corinna Vinschen
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=000180322500 rbx=00018031FCF8 rcx=
> rdx=0003 rsi=0003 rdi=0003
> r8 =001F r9 =00FE r10=000180204E70
> r11=C892 r12= r13=0003
> r14=0001 r15=
> rbp=0018 rsp=CAA0
> 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


signature.asc
Description: PGP signature


Re: Ping crashes

2018-10-29 Thread Takashi Yano
Hello, Anton.

I'm a maintainer of ping package. Thank you for your report.

Ping requires administrator privilege in windows OSs older than Windows 10
build 14926. In such OSs, ping should result in error:
'ping: Lacking privilege for raw socket.'

However, with cygwin 2.11.0 or later, it seems that ping crashes with
segmentation fault in the above case, as you reported.

With cygwin 2.10.0, ping does not cause segmentation fault.

I will look into this problem.

On Sat, 27 Oct 2018 15:25:50 +
"Lavrentiev, Anton (NIH/NLM/NCBI)" 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=000180322500 rbx=00018031FCF8 rcx=
> rdx=0003 rsi=0003 rdi=0003
> r8 =001F r9 =00FE r10=000180204E70
> r11=C892 r12= r13=0003
> r14=0001 r15=
> rbp=0018 rsp=CAA0
> program=C:\cygwin64\bin\ping.exe, pid 6496, thread main
> cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B
> 
> --
> 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
> 


-- 
Takashi Yano 

--
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: Ping crashes

2018-10-27 Thread Houder
On Sat, 27 Oct 2018 15:25:50, X 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)

Related?

https://sourceware.org/ml/cygwin/2018-08/msg00124.html
( Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.11.0-0.1 )

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



Re: Ping crashes

2018-10-27 Thread Houder
On Sat, 27 Oct 2018 15:25:50, X 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