kotovalexarian/free_mutant
1
0
Fork 0
Code Releases Activity

Update information about the MRI segfault problem

Browse source
This commit is contained in:
Markus Schirp 2015-03-14 00:38:24 +00:00
parent b069a0ac58
commit dc0e7b6c7b
1 changed files with 7 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
README.md
View file

@ -87,10 +87,8 @@ The Crash / Stuck Problem (MRI)
-------------------------------
Mutations generated by mutant can cause MRI to enter VM states its not prepared for.
All MRI versions above 1.9 are affected by this depending on your compiler flags, compiler version,
and OS scheduling behavior.
It seems that https://github.com/ruby/ruby/commit/8fe95fea9d238a6deb70c8953ceb3a28a67f4636 fixes the problem (unlreleased). So in doubht you have currently to run muant against latest head / trunk.
All MRI versions > 1.9 and < 2.2.1 are affected by this depending on your compiler flags,
compiler version, and OS scheduling behavior.
This can have the following unintended effects:
@ -107,8 +105,11 @@ This can have the following unintended effects:
References:
* MRI fix: https://github.com/ruby/ruby/commit/8fe95fea9d238a6deb70c8953ceb3a28a67f4636
* MRI backport (to 2.2.1): https://github.com/ruby/ruby/commit/8fe95fea9d238a6deb70c8953ceb3a28a67f4636
* Mutant bug: https://github.com/mbj/mutant/issues/265
* Upstream bug: https://bugs.ruby-lang.org/issues/10460
* Upstream bug redmine: https://bugs.ruby-lang.org/issues/10460
* Upstream bug GH: https://github.com/ruby/ruby/pull/822
Examples
--------
@ -152,7 +153,7 @@ Assuming you are using rspec, you can mutation test Rails models by adding the f
group :test do
gem 'mutant'
gem 'mutant-rspec'
end
end
```
Next, run bundle and comment out ```require 'rspec/autorun'``` from your spec_helper.rb file. Having done so you should be able to use commands like the following: