RE: Perl Term::ReadKey from empty scalar Segfaults under cygwin only (1.7.32 x86_64)

2015-08-25 Thread Luke Goodsell
Hi Achim, > The stacktrace is useless, but if you run this under strace you'll also see a > message that doesn't make it to the output otherwise: That arises from the subsequent print statement, which is never reached under cygwin. Alternative command that eliminates that warning: perl -MTerm

RE: Perl Term::ReadKey from empty scalar Segfaults under cygwin only (1.7.32 x86_64)

2015-08-25 Thread Luke Goodsell
Hi Marco, > $ perl -MTerm::ReadKey -E 'my $input = "\0" ; open(my $stdin, "<", \$input) > or die "failed to open: $!"; local *STDIN = $stdin; ReadMode "raw"; my > $response = ReadKey(1, \*STDIN); ReadMode "normal"; print "Got > \"$response\"\n";' > Got "" I get: > Got " " ... whereas I wou

Perl Term::ReadKey from empty scalar Segfaults under cygwin only (1.7.32 x86_64)

2015-08-25 Thread Luke Goodsell
Hi, Please can you help me to diagnose this issue? Attempting Perl Term::ReadKey from an empty string under Cygwin causes perl to segmentation fault. The same command on Debian, or with a non-empty string, works fine. Example command: > perl -MTerm::ReadKey -e 'my $input = ""; open(my $stdin,