From: nobu@ruby-lang.org
To: ruby-core@ruby-lang.org
Subject: [ruby-core:70396] [Ruby trunk - Bug #11444] STDIN.each_codepoint hangs indefinitely on certain codepoints
Date: Sat, 15 Aug 2015 01:13:15 +0000 [thread overview]
Message-ID: <redmine.journal-53797.20150815011314.b233583d9ee0af60@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-11444.20150814054033@ruby-lang.org
Issue #11444 has been updated by Nobuyoshi Nakada.
Description updated
Backport changed from 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN to 2.0.0: REQUIRED, 2.1: REQUIRED, 2.2: REQUIRED
----------------------------------------
Bug #11444: STDIN.each_codepoint hangs indefinitely on certain codepoints
https://bugs.ruby-lang.org/issues/11444#change-53797
* Author: Andrew Cantino
* Status: Open
* Priority: Normal
* Assignee:
* ruby -v: ruby 2.3.0dev (2015-08-13 trunk 51569) [x86_64-linux]
* Backport: 2.0.0: REQUIRED, 2.1: REQUIRED, 2.2: REQUIRED
----------------------------------------
Piping certain Unicode data into Ruby and calling `each_codepoint` on `STDIN` results in a hang. Control-c does not exit, but control-z will. I've tested this in 2.2.0, 2.2.2, and trunk.
Please see https://gist.github.com/cantino/48f977bee6a39e33f80f for reproduction. There is an example file with various Unicode Emoji characters in it (borrowed from http://apps.timwhitlock.info/emoji/tables/unicode).
I'd like to help fix this if anyone can point me in the right direction. I fiddled with the file until I found a state where it works if one character is removed from the front of the file, so hopefully that's useful information.
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2015-08-15 0:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-11444.20150814054033@ruby-lang.org>
2015-08-14 5:40 ` [ruby-core:70379] [Ruby trunk - Bug #11444] [Open] STDIN.each_codepoint hangs indefinitely on certain codepoints andrew
2015-08-15 1:13 ` nobu [this message]
2015-08-15 3:30 ` [ruby-core:70397] [Ruby trunk - Bug #11444] " andrew
2015-11-29 8:22 ` [ruby-core:71732] " nagachika00
2015-11-29 23:58 ` [ruby-core:71739] " usa
2015-11-30 10:51 ` [ruby-core:71747] " nagachika00
2015-11-30 17:36 ` [ruby-core:71761] " nagachika00
2015-12-01 8:01 ` [ruby-core:71776] " usa
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-53797.20150815011314.b233583d9ee0af60@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/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).