[#35027] [Ruby 1.9-Bug#4352][Open] [patch] Fix eval(s, b) backtrace; make eval(s, b) consistent with eval(s) — "James M. Lawrence" <redmine@...>

Bug #4352: [patch] Fix eval(s, b) backtrace; make eval(s, b) consistent with eval(s)

16 messages 2011/02/01

[#35114] [Ruby 1.9-Bug#4373][Open] http.rb:677: [BUG] Segmentation fault — Christian Fazzini <redmine@...>

Bug #4373: http.rb:677: [BUG] Segmentation fault

59 messages 2011/02/06

[#35171] [Ruby 1.9-Bug#4386][Open] encoding: directive does not affect regex expressions — mathew murphy <redmine@...>

Bug #4386: encoding: directive does not affect regex expressions

9 messages 2011/02/09

[#35237] [Ruby 1.9-Bug#4400][Open] nested at_exit hooks run in strange order — Suraj Kurapati <redmine@...>

Bug #4400: nested at_exit hooks run in strange order

12 messages 2011/02/15

[ruby-core:35358] Re: eval'ing large strings runs out of stack space?

From: Ryan Davis <ryand-ruby@...>
Date: 2011-02-24 01:55:16 UTC
List: ruby-core #35358
On Feb 23, 2011, at 17:02 , Martin J. Dst wrote:

> Hello Roger,
> 
> On 2011/02/24 5:28, Roger Pack wrote:
>> Hello all.
>> This code:
>> 
>> eval (['000000000']*500000).inspect
> 
> This doesn't result in a large string, but in a large array.

I think he's referring to the inspect.

This works fine in 1.8:

10003 % ruby19 -v -e 'eval (["000000000"]*500000).inspect'
ruby 1.9.2p136 (2010-12-25 revision 30365) [x86_64-darwin10.5.0]
(eval):0: stack level too deep (SystemStackError)
10004 % ruby -v -e 'eval (["000000000"]*500000).inspect'
ruby 1.8.7 (2009-06-12 patchlevel 174) [universal-darwin10.0]
10005 %

In This Thread