From: Yui NARUSE <naruse@...>
Date: 2012-01-11T02:58:40+09:00
Subject: [ruby-core:42041] [ruby-trunk - Bug #5867][Closed] Segfault with (likely) the new GC on OSX


Issue #5867 has been updated by Yui NARUSE.

Status changed from Open to Closed


----------------------------------------
Bug #5867: Segfault with (likely) the new GC on OSX
https://bugs.ruby-lang.org/issues/5867

Author: Benoit Daloze
Status: Closed
Priority: Normal
Assignee: 
Category: 
Target version: 
ruby -v: ruby 2.0.0dev (2012-01-08 trunk 34231) [x86_64-darwin10.8.0]


Hello,

I tried the new GC yesterday, and experienced a few segfaults.
I tried again with r34221 (the only significant revisions between this and r34231 are GC-related) and did not see any problem in ~2000 runs. I tried on Linux and saw no problem in ~30000 tries.

Unfortunately, it happens rather rarely, about once in 200 times at me.
It seems to always happen at the same spot.

Here the way I used to produce them:

git clone git://github.com/eregon/epath.git
cd epath
gem i rspec

path/to/ruby-r34231 -rrake -e "Rake.application.run"
 # or
ruby -e 'i=0; while system("path/to/ruby-r34231 -rrake -e \"Rake.application.run\""); p i+=1; end'

I attach a few crashlogs and a gdb backtrace. I can also provide a core dump.
I tried with GC.stress=true once but it worked well. I saw once what was likely memory-corruption effects.
I tried on another project and did not see anything abnormal, `make test-all` also passed.


-- 
http://bugs.ruby-lang.org/