From: nobu@...
Date: 2015-02-25T01:06:23+00:00
Subject: [ruby-core:68292] [Ruby trunk - Bug #10899] [Feedback] ruby 2.2.0 darwin crash (in ripper?)

Issue #10899 has been updated by Nobuyoshi Nakada.

File bug-10899.log added
Description updated
Status changed from Open to Feedback

Could you compile with debugging options?
And, if possible, can it reproduce with the trunk?

----------------------------------------
Bug #10899: ruby 2.2.0 darwin crash (in ripper?)
https://bugs.ruby-lang.org/issues/10899#change-51646

* Author: Matthias Bauer
* Status: Feedback
* Priority: Normal
* Assignee: 
* ruby -v: ruby 2.2.0p0 (2014-12-25 revision 49005) [x86_64-darwin14]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
I get a ruby crash when running metric_fu on a ~20k LOC ruby on rails app.
The crash happens in the `rails_best_practices` metric, but only when running multiple metrics (using `metric_fu -r`, which runs all).
It does not happen when running only a subset of metrics that includes `rails_best_practices`.
I have not been able to narrow it down further, but it seems that the crash originates in ext/ripper.

~~~
/Users/moeffju/.rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/code_analyzer-0.4.5/lib/code_analyzer/checking_visitor/default.rb:42: [BUG] Segmentation fault at 0x00000000037280
(snip)
~~~


---Files--------------------------------
ruby_2015-02-24-163341_Sgian-Dubh.crash (16.3 KB)
bug-10899.log (92.3 KB)


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