[#62297] Re: [ruby-cvs:52906] nari:r45760 (trunk): * gc.c (gc_after_sweep): suppress unnecessary expanding heap. — Eric Wong <normalperson@...>
nari@ruby-lang.org wrote:
7 messages
2014/05/02
[#62307] Re: [ruby-cvs:52906] nari:r45760 (trunk): * gc.c (gc_after_sweep): suppress unnecessary expanding heap.
— SASADA Koichi <ko1@...>
2014/05/03
(2014/05/03 4:41), Eric Wong wrote:
[#62402] Re: [ruby-cvs:52906] nari:r45760 (trunk): * gc.c (gc_after_sweep): suppress unnecessary expanding heap.
— Eric Wong <normalperson@...>
2014/05/05
SASADA Koichi <ko1@atdot.net> wrote:
[#62523] [ruby-trunk - Feature #9632] [PATCH 0/2] speedup IO#close with linked-list from ccan — ko1@...
Issue #9632 has been updated by Koichi Sasada.
3 messages
2014/05/11
[#62556] doxygen (Re: Re: [ruby-trunk - Feature #9632] [PATCH 0/2] speedup IO#close with linked-list from ccan) — Tanaka Akira <akr@...>
2014-05-11 8:50 GMT+09:00 Eric Wong <normalperson@yhbt.net>:
3 messages
2014/05/13
[#62727] [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl — Eric Wong <normalperson@...>
rb_unlink_method_entry may cause old_me to be swept before the new
7 messages
2014/05/24
[#63039] Re: [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl
— SASADA Koichi <ko1@...>
2014/06/10
Hi,
[#63077] Re: [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl
— Eric Wong <normalperson@...>
2014/06/10
SASADA Koichi <ko1@atdot.net> wrote:
[#63086] Re: [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl
— SASADA Koichi <ko1@...>
2014/06/11
(2014/06/11 4:47), Eric Wong wrote:
[#63087] Re: [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl
— Eric Wong <normalperson@...>
2014/06/11
SASADA Koichi <ko1@atdot.net> wrote:
[#62862] [RFC] README.EXT: document rb_gc_register_mark_object — Eric Wong <normalperson@...>
Any comment on officially supporting this as part of the C API?
5 messages
2014/05/30
[ruby-core:62491] [ruby-trunk - Bug #9751] Process.wait does not work correctly in a thread
From:
normalperson@...
Date:
2014-05-10 01:28:50 UTC
List:
ruby-core #62491
Issue #9751 has been updated by Eric Wong.
sam.saffron@gmail.com wrote:
> def test
> if pid = fork
<snip>
> else
> sleep 3
> puts "exiting child"
> exit 0
A workaround is to use exit!(0) in the child.
Normal "exit" may be buggy, looking into it.
> end
> end
----------------------------------------
Bug #9751: Process.wait does not work correctly in a thread
https://bugs.ruby-lang.org/issues/9751#change-46654
* Author: Sam Saffron
* Status: Open
* Priority: Normal
* Assignee:
* Category:
* Target version:
* ruby -v: 1.9, 2.0, 2.1, 2.2
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
The following code fails under Ruby 1.9+, used to work on 1.8 with green threads
```
def test
if pid = fork
puts "child pid is #{pid} waiting ..."
begin
Process.wait(pid)
puts "child exited"
rescue => e
p e
end
else
sleep 3
puts "exiting child"
exit 0
end
end
# this works as expected
test
puts "testing in thread"
# this will hang
Thread.new do
test
end.join
```
Additionally on SIGINT I am seeing a zombie + [BUG] pthread_mutex_lock: Invalid argument (EINVAL)
--
https://bugs.ruby-lang.org/