From: ko1@...
Date: 2015-12-16T18:28:58+00:00
Subject: [ruby-core:72191] [Ruby trunk - Bug #11657] Abort Trap 6 when	running a test suite

Issue #11657 has been updated by Koichi Sasada.


nagachika-san:

Ruby 2.2 has same problem. Here is a patch for ruby 2.2.
Ruby 2.1 and before don't have.

```diff
Index: vm_insnhelper.c
===================================================================
--- vm_insnhelper.c	(revision 53165)
+++ vm_insnhelper.c	(working copy)
@@ -1691,7 +1691,7 @@ vm_call_method(rb_thread_t *th, rb_contr
 		CALLER_SETUP_ARG(cfp, ci);
 		rb_check_arity(ci->argc, 1, 1);
 		ci->aux.index = 0;
-		CI_SET_FASTPATH(ci, vm_call_attrset, enable_fastpath && !(ci->flag & VM_CALL_ARGS_SPLAT));
+		CI_SET_FASTPATH(ci, vm_call_attrset, enable_fastpath && !(ci->flag & VM_CALL_ARGS_SPLAT) && ci->kw_arg == NULL);
 		return vm_call_attrset(th, cfp, ci);
 	      }
 	      case VM_METHOD_TYPE_IVAR:{
```


----------------------------------------
Bug #11657: Abort Trap 6 when running a test suite
https://bugs.ruby-lang.org/issues/11657#change-55603

* Author: Andrew Hodgkinson
* Status: Closed
* Priority: Normal
* Assignee: Koichi Sasada
* 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/