From: Yusuke Endoh Date: 2010-05-13T21:47:02+09:00 Subject: [ruby-core:30209] [Bug #3286] segfault in method_missing -> method -> method_missing recursive loop Issue #3286 has been updated by Yusuke Endoh. Target version set to 1.9.2 Hi, This duplicates #1813. This issue also occurs on trunk. Essentially, infinite recursion may cause segv. The segv is rescued by using sigaltstack on Linux, but it will not on platform where sigaltstack is not available (such as windows). So if you want to write a portable ruby script, you should not depend on SystemStackError. Even in Linux, sigaltstack is set only for main thread. The segv that occurs on sub threads leads to core dump. I don't know the reason why sigaltstack is not used on sub threads, but I guess it is merely forgotten. -- Yusuke Endoh ---------------------------------------- http://redmine.ruby-lang.org/issues/show/3286 ---------------------------------------- http://redmine.ruby-lang.org