[#87467] [Ruby trunk Bug#14841] Very rarely IO#readpartial does not raise EOFError — mofezilla@...
Issue #14841 has been reported by hirura (Hiroyuki URANISHI).
3 messages
2018/06/10
[#87515] [Ruby trunk Bug#14841] Very rarely IO#readpartial does not raise EOFError — hirura@...
Issue #14841 has been updated by hirura (Hiroyuki URANISHI).
7 messages
2018/06/19
[#87516] Re: [Ruby trunk Bug#14841] Very rarely IO#readpartial does not raise EOFError
— Eric Wong <normalperson@...>
2018/06/19
hirura@gmail.com wrote:
[#87517] Re: [Ruby trunk Bug#14841] Very rarely IO#readpartial does not raise EOFError
— Eric Wong <normalperson@...>
2018/06/19
Sorry, I left this out: If you can reproduce it again, can you
[#87519] Re: [Ruby trunk Bug#14841] Very rarely IO#readpartial does not raise EOFError
— hirura <hirura@...>
2018/06/19
Hi Eric,
[#87521] Re: [Ruby trunk Bug#14841] Very rarely IO#readpartial does not raise EOFError
— Eric Wong <normalperson@...>
2018/06/19
hirura <hirura@gmail.com> wrote:
[#87541] [Ruby trunk Feature#14859] [PATCH] implement Timeout in VM — normalperson@...
Issue #14859 has been reported by normalperson (Eric Wong).
4 messages
2018/06/21
[#87605] [Ruby trunk Bug#14867] Process.wait can wait for MJIT compiler process — takashikkbn@...
Issue #14867 has been reported by k0kubun (Takashi Kokubun).
3 messages
2018/06/23
[#87614] [Ruby trunk Bug#14867] Process.wait can wait for MJIT compiler process — normalperson@...
Issue #14867 has been updated by normalperson (Eric Wong).
4 messages
2018/06/23
[#87631] [Ruby trunk Bug#14867] Process.wait can wait for MJIT compiler process — takashikkbn@...
Issue #14867 has been updated by k0kubun (Takashi Kokubun).
5 messages
2018/06/25
[#87635] Re: [Ruby trunk Bug#14867] Process.wait can wait for MJIT compiler process
— Eric Wong <normalperson@...>
2018/06/25
takashikkbn@gmail.com wrote:
[#87665] [Ruby trunk Bug#14867] Process.wait can wait for MJIT compiler process — eregontp@...
Issue #14867 has been updated by Eregon (Benoit Daloze).
4 messages
2018/06/28
[#87710] [Ruby trunk Bug#14867] Process.wait can wait for MJIT compiler process — Greg.mpls@...
Issue #14867 has been updated by MSP-Greg (Greg L).
3 messages
2018/06/30
[ruby-core:87591] [Ruby trunk Bug#14864] some old linux has no O_CLOEXEC
From:
wangpeiwen19920808@...
Date:
2018-06-22 06:03:35 UTC
List:
ruby-core #87591
Issue #14864 has been reported by wangpeiwen (沛文 王). ---------------------------------------- Bug #14864: some old linux has no O_CLOEXEC https://bugs.ruby-lang.org/issues/14864 * Author: wangpeiwen (沛文 王) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: 2.5.1 * Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN ---------------------------------------- I get some error when building ruby on suse 10, ~~~ compiling dir.c dir.c: In function ‘nogvl_opendir_at’: dir.c:1439: error: ‘O_CLOEXEC’ undeclared (first use in this function) dir.c:1439: error: (Each undeclared identifier is reported only once dir.c:1439: error: for each function it appears in.) make: *** [Makefile:398: dir.o] Error 1 ~~~ and I see some "ifdef O_CLOEXEC" in io.c and etc. ~~~ ext/dbm/dbm.c:169:29: * gdbm 1.10 works with O_CLOEXEC. gdbm 1.9.1 silently ignore it. ext/dbm/dbm.c:171:9:#ifndef O_CLOEXEC ext/dbm/dbm.c:172:12:# define O_CLOEXEC 0 ext/dbm/dbm.c:177:49: dbm = dbm_open(RSTRING_PTR(file), flags|O_CLOEXEC, mode); ext/dbm/dbm.c:182:62: dbm = dbm_open(RSTRING_PTR(file), O_RDWR|O_CREAT|O_CLOEXEC, mode); ext/dbm/dbm.c:185:54: dbm = dbm_open(RSTRING_PTR(file), O_RDWR|O_CLOEXEC, 0); ext/dbm/dbm.c:188:56: dbm = dbm_open(RSTRING_PTR(file), O_RDONLY|O_CLOEXEC, 0); ext/sdbm/_sdbm.c:228:8:#ifdef O_CLOEXEC ext/sdbm/_sdbm.c:229:18: flags |= O_CLOEXEC; ext/pty/pty.c:257:38: /* FreeBSD 9.2 or later supports O_CLOEXEC ext/pty/pty.c:266:14:# if defined(O_CLOEXEC) ext/pty/pty.c:268:51: * So version dependency on GNU/Linux is same as O_CLOEXEC with open(). ext/pty/pty.c:269:5: * O_CLOEXEC is available since Linux 2.6.23. Linux 2.6.18 silently ignore it. */ ext/pty/pty.c:270:11: flags |= O_CLOEXEC; dir.c:1439:41: const int opendir_flags = (O_RDONLY|O_CLOEXEC| io.c:238:13:#if defined(O_CLOEXEC) && defined(F_GETFD) io.c:246:27:#endif /* fall through if O_CLOEXEC does not work: */ io.c:257:8:#ifdef O_CLOEXEC io.c:258:8: /* O_CLOEXEC is available since Linux 2.6.23. Linux 2.6.18 silently ignore it. */ io.c:259:14: flags |= O_CLOEXEC; io.c:295:35:#if defined(HAVE_DUP3) && defined(O_CLOEXEC) io.c:298:38: ret = dup3(oldfd, newfd, O_CLOEXEC); io.c:327:29: ret = pipe2(fildes, O_CLOEXEC); ~~~ should we add ifdef in dir.c for building on some platform without O_CLOEXEC -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>