[ruby-core:98885] [Ruby master Bug#16771] Segmentation fault when inspecting a bound method

Issue #16771 has been updated by jeremyevans0 (Jeremy Evans).


decuplet (Nikita Shilnikov) wrote in #note-4:
> @jeremyevans0 was this fixed? I can't find any references to this issue from the repo, perhaps I'm missing something.

It's fixed in master, so the issue is closed, but the flag to backport to 2.7 is set to required.  This is our standard way to mark issues for backporting.  I'll see if I can bisect to find the commit that fixes this.

----------------------------------------
Bug #16771: Segmentation fault when inspecting a bound method
https://bugs.ruby-lang.org/issues/16771#change-86262

* Author: decuplet (Nikita Shilnikov)
* Status: Closed
* Priority: Normal
* ruby -v: 2.7.1
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: REQUIRED
----------------------------------------
This piece of code leads to a crash in ruby 2.7.1.

```ruby
bound_method = Kernel.instance_method(:respond_to?).bind(Object.new)
100000.times { bound_method.inspect }
```

I cannot reproduce the error in 2.7.0 so this must be new.
I attached the output, didn't bother with the crash report log, though. It should be easily reproducible since I found it on CI which runs a different OS.

---Files--------------------------------
output.txt (41.3 KB)


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

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