Project

General

Profile

Bug #13324

IRB Segmentation Fault from eval infinite loop

Added by srodman7689@gmail.com (Sean Rodman) over 2 years ago. Updated about 2 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
-
ruby -v:
ruby 2.3.0p0 (2015-12-25 revision 53290) [x86_64-darwin15]
[ruby-core:80209]

Description

I am not sure if this has already been taken care of or not but I am using ruby 2.3.0 and irb 0.9.6(09/06/30) and when I run the below code I get a segmentation fault

a = "eval a"; eval a

when running the same code with just the ruby interpreter I get the below error which is what I would expect

-e:1:in `eval': stack level too deep (SystemStackError)
    from (eval):1:in `<main>'
    from (eval):1:in `eval'
    from (eval):1:in `<main>'
    from (eval):1:in `eval'
    from (eval):1:in `<main>'
    from (eval):1:in `eval'
    from (eval):1:in `<main>'
    from (eval):1:in `eval'
     ... 9507 levels...
    from (eval):1:in `eval'
    from (eval):1:in `<main>'
    from -e:1:in `eval'
    from -e:1:in `<main>'

History

Updated by srodman7689@gmail.com (Sean Rodman) over 2 years ago

The command I use to run it directly on the ruby interpreter is ruby -e "a = \"eval a\"; eval a"

#2

Updated by nobu (Nobuyoshi Nakada) over 2 years ago

  • Description updated (diff)

Updated by ko1 (Koichi Sasada) over 2 years ago

  • Status changed from Open to Closed

Fundamentally, we can't control machine stack overflow.
We will improve the situation (but can't solve completely).

Updated by srodman7689@gmail.com (Sean Rodman) about 2 years ago

  • Status changed from Closed to Open

The issue is not the stack overflow but the segmentation fault I described when running the same code in the above listed irb version.

#5

Updated by ko1 (Koichi Sasada) about 2 years ago

  • Status changed from Open to Closed

srodman7689@gmail.com (Sean Rodman) wrote:

The issue is not the stack overflow but the segmentation fault I described when running the same code in the above listed irb version.

SEGV because of machine stack overflow.

#6

Updated by usa (Usaku NAKAMURA) about 2 years ago

  • Status changed from Closed to Rejected

Also available in: Atom PDF