Bug #13324: IRB Segmentation Fault from eval infinite loop

• Status: Rejected
• Assignee: -
• Target version: -
• ruby -v: ruby 2.3.0p0 (2015-12-25 revision 53290) [x86_64-darwin15]
• Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN

[[e-mail] (Sean Rodman)]

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>'

[[e-mail] (Sean Rodman)]

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

[nobu (Nobuyoshi Nakada)]

• Description updated (diff)

[ko1 (Koichi Sasada)]

• Status changed from Open to Closed

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

[[e-mail] (Sean Rodman)]

• 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.

[ko1 (Koichi Sasada)]

• Status changed from Open to Closed

[e-mail] (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.

[usa (Usaku NAKAMURA)]

• Status changed from Closed to Rejected