From: "jgraichen (Jan Graichen)" <jgraichen@...>
Date: 2014-01-07T00:36:28+09:00
Subject: [ruby-core:59596] [ruby-trunk - Bug #9315] Segfault when calling	super in rspec mocks with and_call_original [linux]


Issue #9315 has been updated by jgraichen (Jan Graichen).


=begin
Yes, (({ruby 2.2.0dev (2014-01-06 trunk 44510) [x86_64-linux]})) indeed works. Looks somehow I missed the most important head. Sorry.

At least the error on current 2.0.0-head seems interesting, should I open another bug for it?
=end

----------------------------------------
Bug #9315: Segfault when calling super in rspec mocks with and_call_original [linux]
https://bugs.ruby-lang.org/issues/9315#change-44126

Author: jgraichen (Jan Graichen)
Status: Closed
Priority: Normal
Assignee: nobu (Nobuyoshi Nakada)
Category: 
Target version: 
ruby -v: ruby 2.1.0p0 (2013-12-25 revision 44422) [x86_64-linux]
Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN


I've tried running my test suite [1] on Ruby 2.1 resulting in segmentation faults. I've created a smaller rspec test [2] reproducing the segfault. I still haven't found a way to reproduce the segfault without rspec mocks. Run the example via `rspec test.rb`. Same script on Ruby 2.0 works. Used linux is a Debian Sid.

[1] https://travis-ci.org/jgraichen/acfs/jobs/16069122#L87
[2] https://gist.github.com/jgraichen/8159849

I've attached the segfault output.


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