[#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-Bugs-11134 ] Init_stack and ruby_init_stack fail to reinit stack (threads problem?)
Bugs item #11134, was opened at 2007-05-26 04:14 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=1698&aid=11134&group_id=426 Category: Core Group: 1.8.6 >Status: Closed Resolution: None Priority: 3 Submitted By: Gonzalo Garramuno (gga) >Assigned to: Yukihiro Matsumoto (matz) Summary: Init_stack and ruby_init_stack fail to reinit stack (threads problem?) Initial Comment: On an AMD64 box at least (albeit probably others), Init_stack and ruby_init_stack can fail to reinitialize the stack correctly. This problem can happen when Init_stack is invoked from two different places, such as two different C threads (or two different DSOs). At least, that's as far as I was able to reproduce the problem. This problem is also present in the 1.9 branch. The problem is that in those cases the STACK_UPPER() in those functions can fail incorrectly. This can later lead to ruby incorrectly thinking it has run of stack space or to mark incorrectly some VALUEs. There's the need for an init stack function that works reliably across threads, or, alternatively, for one that does not do the STACK_UPPER() check. Here's a trace (with some printfs added to Init_stack and ruby_init_stack to show the problems). This is Maya running its renderer which invokes ruby as a shading language. ruby_init_stack: (nil) at START ruby_init_stack: should reset to 0x7fffb12eb980 ruby_init_stack: 0x7fffb12eb980 at END Init_stack: 0x7fffb12eb980 at START Init_stack should reset to: 0x7fffb12eb964 Init_stack: 0x7fffb12eb980 at END -- ** NOT RESET, but correct ** mark stack 0x7fffb12eb980 - 0x7fffb12e7820- MARKED Starting Rendering /home/gga/maya/projects/default/images/untitled.iff. Rendering current frame. ** this inits a new thread ** ruby_init_stack: 0x7fffb12eb980 at START ruby_init_stack: should reset to 0x418021d0 ruby_init_stack: 0x7fffb12eb980 at END -- **NOT RESET, NOT CORRECT ** ---------------------------------------------------------------------- >Comment By: Yukihiro Matsumoto (matz) Date: 2007-05-26 10:18 Message: In Ruby 1.8, ruby_init_stack() does not suppose to be called twice. Re-initialization is not available. Nor it does not support work with native threading (unless Ruby interpreter runs on single thread). Wait for 1.9 if you want to work with native thread. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=1698&aid=11134&group_id=426