Issue #11928 has been updated by _ wanabe.


This script still causes SEGV.
Confirmed with `ruby 2.4.0dev (2016-01-13 trunk 53518) [x86_64-darwin15]` and `ruby 2.4.0dev (2016-01-13 trunk 53518) [x86_64-linux]`.

```
->{
  ->{
    ->{
      eval <<-EOS
        class Segfault
          at_exit { Segfault.new.segfault } 

          define_method :segfault do
            GC.disable
            0.step do |n|
              n.times do
                (foo rescue $!).local_variables
              end
              GC.start
            end
          end
        end
      EOS
    }.call
  }.call
}.call
```

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

* Author: Adam Wrbel
* Status: Closed
* Priority: Normal
* Assignee: 
* 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>