From: Bob Hutchison <hutch@...>
Date: 2006-12-02T01:42:22+09:00
Subject: Re: Segmentation fault, proc, eval, long string [Work Around]


On 1-Dec-06, at 7:31 AM, Pit Capitain wrote:

> Bob, you can use parsetree to dump the AST of the generated proc.  
> I'm sure you'll see the deep nesting of the nodes.

Oh, very interesting. Yes indeed it gets kinda deep there :-) Thanks!

So the 'solution' is to set the stack size bigger (ulimit -s 20000  
works up to a much larger number). But this 'solution' does not make  
me very happy. First the stack size is the same on all the machines  
that I'm using, so while this fixes the machine showing the problem I  
am not entirely convinced. Secondly, all this does is increases the  
depth at which it will fail (and it still does fail). Seems more of a  
work around than a solution.

Any better ideas?

What is actually going on anyway? Is Ruby creating a closure or  
something for each new local variable introduced?

Cheers,
Bob

>
> Regards,
> Pit
>

----
Bob Hutchison                  -- blogs at <http://www.recursive.ca/ 
hutch/>
Recursive Design Inc.          -- <http://www.recursive.ca/>
Raconteur                      -- <http://www.raconteur.info/>
xampl for Ruby                 -- <http://rubyforge.org/projects/xampl/>