public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Luke Goodsell <Luke.Goodsell@ogt.com>
To: Achim Gratz <Stromeko@NexGo.DE>, "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Perl Term::ReadKey from empty scalar Segfaults under cygwin only (1.7.32 x86_64)
Date: Tue, 25 Aug 2015 09:52:00 -0000	[thread overview]
Message-ID: <59C49FE16E416F46873F86D530DA80520BD7A0@ExchangeServer.internal.ogtip.com> (raw)
In-Reply-To: <loom.20150825T113314-983@post.gmane.org>

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::ReadKey -we 'my $input = ""; open(my $stdin, "<", \$input) or die "failed to open: $!"; local *STDIN = $stdin; ReadMode "raw"; my $response = ReadKey(1, \*STDIN); ReadMode "normal"; if(defined($response)) { print "Got \"$response\"\n"; } else { print "Got undef\n"; }'

> Please report this upstream.

To whom would that be? Perl devs?

Kind regards,
Luke

--
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:[~2015-08-25  9:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25  8:48 Luke Goodsell
2015-08-25  9:17 ` Marco Atzeri
2015-08-25  9:43   ` Luke Goodsell
2015-08-25  9:40 ` Achim Gratz
2015-08-25  9:52   ` Luke Goodsell [this message]
2015-08-25 12:06     ` Achim Gratz

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=59C49FE16E416F46873F86D530DA80520BD7A0@ExchangeServer.internal.ogtip.com \
    --to=luke.goodsell@ogt.com \
    --cc=Stromeko@NexGo.DE \
    --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).