From: arne@...
Date: 2014-11-04T09:43:40+00:00
Subject: [ruby-core:66075] [ruby-trunk - Bug #10460] Segfault instead of	stack level too deep

Issue #10460 has been updated by Arne Brasseur.


Did some more testing on current trunk (trunk@48266)

Depending on the optimization level I get different results. -O0 works correctly, -O1 segfaults, -O2 works correctly, -O3 hangs.

strace of the two problematic versions: 

* -O1: https://gist.github.com/plexus/15b50dbd31574d6c6657
* -O3: https://gist.github.com/plexus/173003e04e71492ac430

I would love to help resolve this but am in way past my comfort zone :) suggestions on how to proceed would be very much appreciated.

----------------------------------------
Bug #10460: Segfault instead of stack level too deep
https://bugs.ruby-lang.org/issues/10460#change-49790

* Author: Arne Brasseur
* Status: Open
* Priority: High
* Assignee: Koichi Sasada
* Category: YARV
* Target version: current: 2.2.0
* ruby -v: ruby 2.2.0dev (2014-10-29 trunk 48188) [x86_64-linux]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN
----------------------------------------
The code to trigger this can be found here: https://gist.github.com/mbj/31163a8e712573877268

Also have a look at the comments there. A lot of different people tried it, in some cases it segfaults, in others it doesn't. It seems to have to do with version of gcc or specific CFLAGS. 

I can reproduce the problem for 2.1.3, 2.1.4, and trunk.



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