[#11073] segfault printing instruction sequence for iterator — <noreply@...>
Bugs item #10527, was opened at 2007-05-02 14:42
Hi,
On Thu, May 10, 2007 at 04:51:18PM +0900, Nobuyoshi Nakada wrote:
Hi,
Hi,
This seems to make valgrind much happier.
On Thu, May 17, 2007 at 11:14:35PM +0900, Paul Brannan wrote:
Hi,
Now 'a' shows up twice in the local table:
Hi,
[#11082] Understanding code: Kernel#require and blocks. — Hugh Sasse <hgs@...>
I'm trying to debug a Rails application which complains about an
On 5/4/07, Hugh Sasse <hgs@dmu.ac.uk> wrote:
On Fri, 4 May 2007, George wrote:
On Fri, May 04, 2007 at 06:18:19PM +0900, Hugh Sasse wrote:
[#11108] pattern for implementation-private constants? — David Flanagan <david@...>
Hi,
I believe there isn't a way, but I don't think it's really necessary. Just
[#11127] Bugs that can be closed — "Jano Svitok" <jan.svitok@...>
I propose closing these bugs as invalid:
[#11145] Rational comparison to 0 fails when denominator is != 1 — <noreply@...>
Bugs item #10739, was opened at 2007-05-10 22:06
Hi,
[#11169] Allow back reference with nest level in Oniguruma for Ruby again — =?ISO-8859-15?Q?Wolfgang_N=E1dasi-Donner?= <wonado@...>
Remark: I posted this text in comp.lang.ruby first, but Matz told me,
Does it make sense or is it required to write this as a RCR?
[#11176] FileUtils.rm_rf misfeature? — johan556@...
Hi!
[#11210] Pathname ascend and descend inclusive parameter — TRANS <transfire@...>
I would like to suggest that Pathname#ascend and Pathname#descend
[#11234] Planning to release 1.8.6 errata — Urabe Shyouhei <shyouhei@...>
Hi all.
On 25/05/07, Urabe Shyouhei <shyouhei@ruby-lang.org> wrote:
[#11252] Init_stack and ruby_init_stack fail to reinit stack (threads problem?) — <noreply@...>
Bugs item #11134, was opened at 2007-05-25 12:14
Hi,
Nobuyoshi Nakada wrote:
[#11255] ruby_1_8_6 build problem (make install-doc) — johan556@...
Hi!
[#11271] providing better support through rubyforge tracker categories — Ryan Davis <ryand-ruby@...>
I'm going to make more categories for the trackers (bugs and patches)
[#11367] BUG: next in lambda: 1.8.6 differs from 1.8.4 and 1.9.0 — David Flanagan <david@...>
A toplevel next statement in a lambda does not return a value in 1.8.6,
[#11368] $2000 USD Reward for help fixing Segmentation Fault in GC — Brent Roman <brent@...>
Hi Brent,
[ ruby-Patches-5111 ] Instability around popen due to missing rb_thread_atfork
Patches item #5111, was opened at 2006-07-18 14:36
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=1700&aid=5111&group_id=426
Category: Ruby1.8
>Group: v1.8.x
Status: Open
Resolution: None
Priority: 3
Submitted By: Jonathan Paisley (jzp)
Assigned to: Nobody (None)
Summary: Instability around popen due to missing rb_thread_atfork
Initial Comment:
A Ruby program with multiple threads making calls to IO.popen (or indirectly via backticks) can get some nasty race conditions if existing threads get a chance to run in the child.
This can happen, for example, if the rb_warn("Insecure world writable dir...") from file.c:path_check_0() gets invoked in the child.
Solution is to add a call to 'rb_thread_atfork()' in the child after fork() in order to kill off those other threads.
On a related theme, it seems like the 'rb_proc_exec' in process.c:pipe_open() should be protected with rb_protect or similar, to prevent any exceptions raised during rb_proc_exec() from being propagated to the soon-to-be-dead main thread in the child process. I'm not familiar enough with use of rb_protect to provide a proper patch for that.
Patch attached and included inline below:
diff -ur orig/ruby/io.c ruby/io.c
--- orig/ruby/io.c 2006-06-26 08:23:47.000000000 +0100
+++ ruby/io.c 2006-07-18 22:27:33.000000000 +0100
@@ -3102,6 +3102,7 @@
retry:
switch ((pid = fork())) {
case 0: /* child */
+ rb_thread_atfork();
if (modef & FMODE_READABLE) {
close(pr[0]);
if (pr[1] != 1) {
----------------------------------------------------------------------
Comment By: Jonathan Paisley (jzp)
Date: 2007-03-18 09:43
Message:
This problem still occurs in ruby-1.8.6. What can be done to get the simple
patch to io.c into 1.8.x?
There was some discussion around the original submission with patches by
Nobu Nakada:
http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-core/8262
----------------------------------------------------------------------
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=1700&aid=5111&group_id=426