Issue #11928 has been updated by Yuki Nishijima.


I was able to replicate it without `did_you_mean`.

1. Save this file as `loader.rb`:

    ```ruby
    -> { require_relative 'segfault' }.call
    ```

2. Save this file as `segfault.rb`:

    ```ruby
    class Segfault
      at_exit { Segfault.new.segfault }

      define_method 'segfault' do
        while true do
          (foo rescue $!).local_variables
        end
      end
    end
    ```

3. Then run:

    ```
    $ ruby --disable-gems loader.rb
    ```

----------------------------------------
Bug #11928: Segmentation fault in did_you_mean extension
https://bugs.ruby-lang.org/issues/11928#change-55971

* Author: Adam Wrbel
* Status: Feedback
* Priority: Normal
* Assignee: Yuki Nishijima
* ruby -v: ruby 2.3.0p0 (2015-12-25 revision 53290) [x86_64-darwin15]
* Backport: 2.3: UNKNOWN
----------------------------------------
I'm getting a segmentation fault in my Rails application test suite if I attempt to use an undefined method/object.

I was not able to reproduce this outside of the complex environment of my application, but hopefully you might be able to figure out what is going on just using the crash logs. I had to filter out lines that contained file paths of my application - fortunately they were only in the "Loaded features" section and not anywhere in C or Ruby backtraces.

---Files--------------------------------
did_you_mean_clean.log (300 KB)
ruby_2015-12-27-133453_iMac.crash (26.4 KB)


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

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>