[#71439] [Ruby trunk - Feature #11339] [PATCH] io.c: avoid kwarg parsing in C API — matz@...
Issue #11339 has been updated by Yukihiro Matsumoto.
7 messages
2015/11/11
[#71473] Re: [Ruby trunk - Feature #11339] [PATCH] io.c: avoid kwarg parsing in C API
— Eric Wong <normalperson@...>
2015/11/13
Entire series for sockets
[#71450] Ruby 2.3.0-preview1 Released — "NARUSE, Yui" <naruse@...>
Hi,
5 messages
2015/11/11
[#71617] [Ruby trunk - Feature #11664] [PATCH] introduce rb_autoload_value to replace rb_autoload — nobu@...
Issue #11664 has been updated by Nobuyoshi Nakada.
3 messages
2015/11/20
[#71721] [Ruby trunk - Feature #11741] Migrate Ruby to Git from Subversion — me@...
Issue #11741 has been updated by Jon Moss.
4 messages
2015/11/28
[ruby-core:71344] [Ruby trunk - Bug #11657] [Open] Abort Trap 6 when running a test suite
From:
ahodgkin@...
Date:
2015-11-05 03:02:50 UTC
List:
ruby-core #71344
Issue #11657 has been reported by Andrew Hodgkinson. ---------------------------------------- Bug #11657: Abort Trap 6 when running a test suite https://bugs.ruby-lang.org/issues/11657 * Author: Andrew Hodgkinson * Status: Open * Priority: Normal * Assignee: ruby-core * ruby -v: ruby 2.2.3p173 (2015-08-18 revision 51636) [x86_64-darwin15] *OR* ruby 2.3.0dev (2015-11-01 trunk 52421) [x86_64-darwin15] * Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN ---------------------------------------- An internal Ruby gem I develop for my company has a test suite that works fine on Ruby 2.1.x but crashes on **2.2.3 and 2.3.0-dev** with: ~~~ [BUG] Stack consistency error (sp: 273, bp: 271) ~~~ I've tried this on both OS X (10.11.1) and a Debian build in a Virtualbox VM to try and eliminate OS X as the problem, with the same results (as in, an abort and a 'stack consistency error' in the logs). I have attached the backtrace log data from both the OS X and Debian builds, from Ruby 2.2.3p173 (though as I say, I did try 2.3.0-dev too and the same stack error arose). At present, the component in question is closed source. We are actually planning to open source it, but it'll be a while. I'm unable to replicate this as some isolated test case at present I'm afraid - it seems quite a lot of "stuff" needs to happen before it dies. ---Files-------------------------------- ruby_crash_osx.log (141 KB) ruby_crash_debian.log (160 KB) -- https://bugs.ruby-lang.org/