Project

General

Profile

Bug #1613

Segfault due to stack overflow

Added by RobertDober (Robert Dober) over 10 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
ruby -v:
ruby 1.9.1p129 (2009-05-12 revision 23412) [i686-linux]
[ruby-core:23813]

Description

=begin
When using a closure or param to cache values for recursive calls, the stack overflow is not caught but segfaults.
=end


Files

closure_segfault.rb (381 Bytes) closure_segfault.rb RobertDober (Robert Dober), 06/12/2009 09:20 AM
noclosure.rb (391 Bytes) noclosure.rb RobertDober (Robert Dober), 06/12/2009 09:20 AM

History

#1

Updated by matz (Yukihiro Matsumoto) over 10 years ago

=begin
Hi,

In message "Re: [ruby-core:23813] [Bug #1613] Segfault due to stack overflow"
on Fri, 12 Jun 2009 09:21:00 +0900, Robert Dober redmine@ruby-lang.org writes:

|When using a closure or param to cache values for recursive calls, the stack overflow is not caught but segfaults.

It is pretty difficult to detect stack overflow 100%, but we will
improve.

                        matz.

=end

#2

Updated by yugui (Yuki Sonoda) about 10 years ago

  • Status changed from Open to Closed
  • % Done changed from 0 to 100

=begin
Applied in changeset r23794.
=end

Also available in: Atom PDF