[#81492] [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid — normalperson@...

Issue #13618 has been reported by normalperson (Eric Wong).

12 messages 2017/06/01

[ruby-core:81615] [Ruby trunk Bug#13324][Closed] IRB Segmentation Fault from eval infinite loop

From: ko1@...
Date: 2017-06-08 01:54:18 UTC
List: ruby-core #81615
Issue #13324 has been updated by ko1 (Koichi Sasada).

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.

----------------------------------------
Bug #13324: IRB Segmentation Fault from eval infinite loop
https://bugs.ruby-lang.org/issues/13324#change-65311

* Author: srodman7689@gmail.com (Sean Rodman)
* Status: Closed
* Priority: Normal
* 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
----------------------------------------
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

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



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

In This Thread

Prev Next