[prev in list] [next in list] [prev in thread] [next in thread]
List: ruby-core
Subject: Re: [BUG] unknown node type 0 - SERIOUS ENOUGH TO MIGRATE AWAY FROM RUBY?
From: Joao Pedrosa <joaopedrosa () gmail ! com>
Date: 2004-12-22 17:23:03
Message-ID: ca24287804122209231f75fb0a () mail ! gmail ! com
[Download RAW message or body]
Hi,
That's a very good news. :-)
Cheers,
Joao
On Wed, 22 Dec 2004 18:43:03 +0900, Andrew Walrond <andrew@walrond.org> wrote:
> On Wednesday 15 December 2004 14:11, Yukihiro Matsumoto wrote:
> >
> > Try recent snapshot. The following change might fix your problem.
> >
> > Mon Dec 13 18:13:52 2004 Tanaka Akira
> >
> > * gc.c (stack_end_address): new function to obtain stack end address.
> > stack_end_address calls __builtin_frame_address(0) to obtain the
> > frame pointer of a stack frame of stack_end_address. The address
> > is the stack pointer of the caller's stack frame.
> > (SET_STACK_END): use stack_end_address.
> > This makes the conservative garbage collector to scan a stack frame
> > of the garbage_collect function itself. This is required because
> > callee-save registers may be stored in the frame.
> > [ruby-dev:25158]
> >
>
> Just an update; Almost a week now and no problems so far on the four servers I
> am testing. I'm getting more optimistic by the day ;)
>
> Andrew Walrond
>
>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic