alk (Aliaksey Kandratsenka)
- Login: alk
- Email: alkondratenko@gmail.com
- Registered on: 01/06/2010
- Last sign in: 05/08/2010
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 0 | 0 | 0 |
Reported issues | 0 | 2 | 2 |
Activity
05/08/2010
- 11:40 PM Backport187 Bug #3100: Lockup in child after fork
- =begin
Pass --enable-pthread to ./configure. That's part of ruby configuration in Debian/Ubuntu.
Latest as of S...
04/06/2010
- 12:22 PM Backport187 Bug #3100: Lockup in child after fork
- =begin
ruby_1_8_7@27173 and ruby_1_8@27224 still hang.
with 1.8.7 branch the backtrace is a bit different
...
04/05/2010
- 08:14 PM Backport187 Bug #3100 (Closed): Lockup in child after fork
- =begin
I was using PTY.spawn and found a bug. I'm attaching a small testcase that at least on 2 my machines gives q...
03/18/2010
- 06:11 PM Backport191 Backport #2564: [patch] re-initialize timer_thread_{lock,cond} after fork
- =begin
The folks who experienced this bug do not experience it anymore. I assume it was kernel bug. This ticket can ...
02/28/2010
- 11:07 PM Backport191 Backport #2564: [patch] re-initialize timer_thread_{lock,cond} after fork
- =begin
I have to admit my mistake again. There is a call to native_thread_join in 1.9.1, it's in rb_thread_stop_time...
02/04/2010
- 04:42 PM Backport191 Backport #2564: [patch] re-initialize timer_thread_{lock,cond} after fork
- =begin
I'm sorry to bother you again, but merging r25629 to 1.9.1 should be really trivial. Without that fix there's...
01/28/2010
- 06:51 PM Backport191 Backport #2564: [patch] re-initialize timer_thread_{lock,cond} after fork
- =begin
Indeed. I was wrong. But there's still bug in 1.9.1. native_stop_timer_thread() doesn't wait till timer threa...
01/27/2010
- 11:47 PM Backport191 Backport #2564: [patch] re-initialize timer_thread_{lock,cond} after fork
- =begin
It seems I'm not stating the problem clearly enough.
What happens:
a) lets suppose timer thread is doing ... - 07:30 AM Backport191 Backport #2564: [patch] re-initialize timer_thread_{lock,cond} after fork
- =begin
No. http://redmine.ruby-lang.org/issues/show/2394 is unrelated.
=end
- 07:28 AM Backport191 Backport #2564: [patch] re-initialize timer_thread_{lock,cond} after fork
- =begin
Yes I can. But I'd like to avoid doing that. Reliable reproduction of such tiny races is not trivial. I have ...
Also available in: Atom