From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ruby-core-bounces@ruby-lang.org>
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 844DA17DBF47
	for <poffice@blade.nagaokaut.ac.jp>; Thu,  9 Oct 2014 17:01:24 +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 BB5E0B5D97F
	for <poffice@blade.nagaokaut.ac.jp>; Thu,  9 Oct 2014 16:45:11 +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 C05BA97A83A
	for <poffice@blade.nagaokaut.ac.jp>; Thu,  9 Oct 2014 16:45:13 +0900 (JST)
X-Virus-Scanned: amavisd-new at nagaokaut.ac.jp
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 IW-d61A-Qr7u for <poffice@blade.nagaokaut.ac.jp>;
	Thu,  9 Oct 2014 16:45:13 +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 A008497A834
	for <poffice@blade.nagaokaut.ac.jp>; Thu,  9 Oct 2014 16:45:13 +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 A42ED952439
	for <poffice@blade.nagaokaut.ac.jp>; Thu,  9 Oct 2014 16:45:11 +0900 (JST)
Received: from [221.186.184.76] (localhost [IPv6:::1])
	by neon.ruby-lang.org (Postfix) with ESMTP id F05C712046F;
	Thu,  9 Oct 2014 16:44:53 +0900 (JST)
X-Original-To: ruby-core@ruby-lang.org
Delivered-To: ruby-core@ruby-lang.org
Received: from dcvr.yhbt.net (dcvr.yhbt.net [64.71.152.64])
 by neon.ruby-lang.org (Postfix) with ESMTP id D614B120444
 for <ruby-core@ruby-lang.org>; Thu,  9 Oct 2014 16:44:49 +0900 (JST)
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
 by dcvr.yhbt.net (Postfix) with ESMTP id 9BCE51F89E;
 Thu,  9 Oct 2014 07:44:48 +0000 (UTC)
Date: Thu, 9 Oct 2014 07:44:48 +0000
From: Eric Wong <normalperson@yhbt.net>
To: Ruby developers <ruby-core@ruby-lang.org>
Message-ID: <20141009074448.GA1000@dcvr.yhbt.net>
References: <redmine.issue-8543.20130619213935@ruby-lang.org>
 <redmine.journal-49316.20141009071824.2f68050c9bd5ea63@ruby-lang.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <redmine.journal-49316.20141009071824.2f68050c9bd5ea63@ruby-lang.org>
X-ML-Name: ruby-core
X-Mail-Count: 65556
Subject: [ruby-core:65556] Re: [ruby-trunk - Feature #8543] rb_iseq_load
X-BeenThere: ruby-core@ruby-lang.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Ruby developers <ruby-core@ruby-lang.org>
List-Id: Ruby developers <ruby-core.ruby-lang.org>
List-Unsubscribe: <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>, 
 <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
List-Post: <mailto:ruby-core@ruby-lang.org>
List-Help: <mailto:ruby-core-request@ruby-lang.org?subject=help>
List-Subscribe: <http://lists.ruby-lang.org/cgi-bin/mailman/listinfo/ruby-core>, 
 <mailto:ruby-core-request@ruby-lang.org?subject=subscribe>
Errors-To: ruby-core-bounces@ruby-lang.org
Sender: "ruby-core" <ruby-core-bounces@ruby-lang.org>

billk@cts.com wrote:
> Sorry to be the squeaky wheel, but I was wondering if there still
> might be a chance to look into this before 2.2 is released?

Not speaking for the rest of ruby-core, but I welcome occasional
reminders like these :)

> I attempted a `git bisect` this evening in the hope of narrowing
> down where the iseq.load problems began -- however I ran into a
> problem of being unable to build ruby-trunk prior to this patch:
> 
> commit 434826c0e9d3e3b48d99a39b7ad7626a6f1ae2eb
> Author: kazu <kazu@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>
> Date:   Wed Jul 31 13:01:57 2013 +0000
> 
>     * parse.y: fix build error with bison-3.0.
> 
> And unfortunately the iseq.load problem already existed by that
> point.

Thanks for that data point, it was before I started mucking with iseq.
Can you try installing/running an older bison?

> (I wonder how best to proceed with the bisect.  I suppose one
> could write a script to attempt to apply the parse.y patch at
> each stage...)

Yes.  "git bisect run" is awesome for scripting these things.