From: ahodgkin@... Date: 2015-12-16T03:26:04+00:00 Subject: [ruby-core:72170] [Ruby trunk - Bug #11657] Abort Trap 6 when running a test suite Issue #11657 has been updated by Andrew Hodgkinson. Nobuyoshi Nakada wrote: > We love to see your "isolated test case". My company has now open sourced the gem in question. The best I've been able to is create a branch with a replicable test case that has as many dependencies cut out as I can get away with, using a random seed that causes the error to happen very early in test execution to try and aid fault analysis. ~~~ git clone -b demonstration/ruby_223_abort_trap_6 https://git@github.com/LoyaltyNZ/hoodoo.git bundle install bundle exec rspec -f d spec/services/middleware/middleware_multi_local_spec.rb:677 -f d --seed 30498 ~~~ This should abort. See "log/test.log" for the stack info. The full test suite won't run at all because I've stripped out so many things, but that particular section of it, with that particular random seed, prompts the abort quickly. If you ask it to run the whole file: ~~~ be rspec -f d spec/services/middleware/middleware_multi_local_spec.rb ~~~ ...then - ignoring any test failures caused by the stripped-out stuff - you'll notice it gets a variable length through before aborting, apparently with no pattern; but no matter how many or few tests seem to run first, the specific line complaining about the fault prior to the crash **is always the same**: ~~~ /.../hoodoo/spec/services/middleware/middleware_multi_local_spec.rb:227: [BUG] Stack consistency error (sp: 224, bp: 222) ~~~ Is there anything else you need to help look into this crash? ---------------------------------------- Bug #11657: Abort Trap 6 when running a test suite https://bugs.ruby-lang.org/issues/11657#change-55581 * Author: Andrew Hodgkinson * Status: Open * 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/