ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: srodman7689@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:81607] [Ruby trunk Bug#13324][Open] IRB Segmentation Fault from eval infinite loop
Date: Wed, 07 Jun 2017 14:18:44 +0000	[thread overview]
Message-ID: <redmine.journal-65305.20170607141844.1fef591fc931b760@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-13324.20170317160135@ruby-lang.org

Issue #13324 has been updated by srodman7689@gmail.com (Sean Rodman).

Status changed from Closed to Open

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

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

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

  parent reply	other threads:[~2017-06-07 14:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-13324.20170317160135@ruby-lang.org>
2017-03-17 16:01 ` [ruby-core:80209] [Ruby trunk Bug#13324] IRB Segmentation Fault from eval infinite loop srodman7689
2017-03-17 16:02 ` [ruby-core:80208] " srodman7689
2017-05-19  6:54 ` [ruby-core:81254] [Ruby trunk Bug#13324][Closed] " ko1
2017-06-07 14:18 ` srodman7689 [this message]
2017-06-08  1:54 ` [ruby-core:81615] " ko1

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.journal-65305.20170607141844.1fef591fc931b760@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).