From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: poffice@blade.nagaokaut.ac.jp Delivered-To: poffice@blade.nagaokaut.ac.jp Received: from kankan.nagaokaut.ac.jp (kankan.nagaokaut.ac.jp [133.44.2.24]) by blade.nagaokaut.ac.jp (Postfix) with ESMTP id 8994F19809ED for ; Mon, 17 Aug 2015 21:24:40 +0900 (JST) Received: from funfun.nagaokaut.ac.jp (funfun.nagaokaut.ac.jp [133.44.2.201]) by kankan.nagaokaut.ac.jp (Postfix) with ESMTP id 5C031B5D9C8 for ; Mon, 17 Aug 2015 22:00:22 +0900 (JST) Received: from funfun.nagaokaut.ac.jp (localhost.nagaokaut.ac.jp [127.0.0.1]) by funfun.nagaokaut.ac.jp (Postfix) with ESMTP id 075A697A839 for ; Mon, 17 Aug 2015 22:00:25 +0900 (JST) X-Virus-Scanned: amavisd-new at nagaokaut.ac.jp Authentication-Results: funfun.nagaokaut.ac.jp (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=sendgrid.me Received: from funfun.nagaokaut.ac.jp ([127.0.0.1]) by funfun.nagaokaut.ac.jp (funfun.nagaokaut.ac.jp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OWHas27mRqzI for ; Mon, 17 Aug 2015 22:00:24 +0900 (JST) Received: from voscc.nagaokaut.ac.jp (voscc.nagaokaut.ac.jp [133.44.1.100]) by funfun.nagaokaut.ac.jp (Postfix) with ESMTP id BF26C97A82B for ; Mon, 17 Aug 2015 22:00:24 +0900 (JST) Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by voscc.nagaokaut.ac.jp (Postfix) with ESMTP id 02283952446 for ; Mon, 17 Aug 2015 22:00:21 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 3596512045A; Mon, 17 Aug 2015 22:00:22 +0900 (JST) X-Original-To: ruby-core@ruby-lang.org Delivered-To: ruby-core@ruby-lang.org Received: from o2.heroku.sendgrid.net (o2.heroku.sendgrid.net [67.228.50.55]) by neon.ruby-lang.org (Postfix) with ESMTPS id 1A8AA120441 for ; Mon, 17 Aug 2015 22:00:17 +0900 (JST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.me; h=from:to:references:subject:mime-version:content-type:content-transfer-encoding:list-id; s=smtpapi; bh=r9ycHcAeLfBxYJC7ckolosEUHPk=; b=mfmrtQj0cimkLwucHz FjWdwtDqU5ql+jrDImzjh6jXByElmMMIduC6nf1GxPMODMwYizqEGFlYAfodfAkp piTxbsxf7iRYmTEzFoTEC0wdQ+VkSTQMCUnUphTitw7T/xDv5GkBecsCYTQBRABm 1WQ66Xu4D3koqaThW3eZJNieo= Received: by filter0691p1mdw1.sendgrid.net with SMTP id filter0691p1mdw1.28566.55D1DADA24 2015-08-17 13:00:10.563634419 +0000 UTC Received: from herokuapp.com (ec2-54-161-199-18.compute-1.amazonaws.com [54.161.199.18]) by ismtpd0006p1iad1.sendgrid.net (SG) with ESMTP id 8TSXHSsWQfuf8lZsBaKNxA for ; Mon, 17 Aug 2015 13:00:10 +0000 (UTC) Date: Mon, 17 Aug 2015 13:00:10 +0000 From: alexinbeijing@gmail.com To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Redmine-MailingListIntegration-Message-Ids: 45039 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 11451 X-Redmine-Issue-Author: alexdowad X-Redmine-Sender: alexdowad X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-SG-EID: ync6xU2WACa70kv/Ymy4QrNMhiuLXJG8OTL2vJD1yS6BcHfQjut8itAGyjOZ+abzk6iMUUXE6D2+xP P+Vx71mkYARB7q2cRk9NQwNO3W1k3Flir3nifnVnKM5wsMfRULkgjRsewqho36AjiCALmChePxl/4i PsHkfSCzKgqesSfJ+fLRrRNpgh/UZIKRcAwb X-ML-Name: ruby-core X-Mail-Count: 70429 Subject: [ruby-core:70429] [Ruby trunk - Bug #11451] MRI crashes with 'Stack inconsistency error' when a method which yields is called recursively in a particular way X-BeenThere: ruby-core@ruby-lang.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Ruby developers List-Id: Ruby developers List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" Issue #11451 has been updated by Alex Dowad. Sorry, I forgot to say... THANKS to Xavier Shay for finding this problem! ---------------------------------------- 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-53838 * Author: Alex Dowad * Status: Open * Priority: Normal * Assignee: * ruby -v: 2.3.0dev, also present in 2.2.2 * Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN ---------------------------------------- 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/