ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: nagachika00@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:71628] [Ruby trunk - Bug #11451] MRI crashes with 'Stack inconsistency error' when a method which yields is called recursively in a particular way
Date: Sun, 22 Nov 2015 15:41:44 +0000	[thread overview]
Message-ID: <redmine.journal-55029.20151122154144.8b0680fa8a0a2be4@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-11451.20150817125902@ruby-lang.org

Issue #11451 has been updated by Tomoyuki Chikanaga.

Backport changed from 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: REQUIRED to 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: DONE

Backported into `ruby_2_2` branch at r52717.

----------------------------------------
Bug #11451: MRI crashes with 'Stack inconsistency error' when a method which yields is called recursively in a particular way
https://bugs.ruby-lang.org/issues/11451#change-55029

* Author: Alex Dowad
* Status: Closed
* Priority: Normal
* Assignee: Koichi Sasada
* ruby -v: 2.3.0dev, also present in 2.2.2
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: DONE
----------------------------------------
Dear Ruby people,

How are you? The other day, someone reported that a gem I maintain was crashing under MRI 2.2.2. I traced it through with GDB, found where it was going wrong, and wrote a tiny little patch which makes the crash go away. (Yay!) Can you look at this and check that this patch won't cause any other problems?

Thanks,
Alex Dowad

---Files--------------------------------
repro.rb (283 Bytes)
0001-Fix-crash-caused-by-recursive-yield-to-blocks-with-d.patch (1.48 KB)


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

      parent reply	other threads:[~2015-11-23 23:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-11451.20150817125902@ruby-lang.org>
2015-08-17 12:59 ` [ruby-core:70428] [Ruby trunk - Bug #11451] [Open] MRI crashes with 'Stack inconsistency error' when a method which yields is called recursively in a particular way alexinbeijing
2015-08-17 13:00 ` [ruby-core:70429] [Ruby trunk - Bug #11451] " alexinbeijing
2015-08-18  3:46 ` [ruby-core:70442] [Ruby trunk - Bug #11451] [Assigned] " nobu
2015-08-21  8:38 ` [ruby-core:70504] [Ruby trunk - Bug #11451] " ko1
2015-11-22 15:41 ` nagachika00 [this message]

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-55029.20151122154144.8b0680fa8a0a2be4@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).