From: Yukihiro Matsumoto <matz@...>
Date: 2006-12-04T22:36:20+09:00
Subject: Re: Segmentation fault, proc, eval, long string [Reproduced]

Hi,

In message "Re: Segmentation fault, proc, eval, long string [Reproduced]"
    on Mon, 4 Dec 2006 21:50:22 +0900, Bob Hutchison <hutch@recursive.ca> writes:

|This is consistent with what I'm seeing. Just before you posted your  
|patch, I made a couple of changes to the application and also  
|replaced the Proc with a method. The changes to the application would  
|reduce the maximum number of local variables by typically one third.  
|The use of a method rather than a Proc avoided the nested parsing and  
|subsequent stack overflow (and is many times faster for large cases).  
|Even with that the application barely fits into the available memory.  
|So if the Proc's local variables cause even a relatively small  
|proportional increase in memory the application is going to get  
|itself killed.
|
|Anyway, with the combination of all of this, and a better linux  
|configuration I think I'll be past this.

Good to know that.  For your information, YARV does not have this
problem by better in-block variable handling.  Another reason to wait
for YARV.

							matz.