Issue #15406 has been updated by tenderlovemaking (Aaron Patterson).


ko1 (Koichi Sasada) wrote:
> This patch will fix.
> Aaron, could you confirm it?

I bisected this and r62851 introduced the issue.  The patch makes sense, so I applied it in r66376.  Thanks ko1!


----------------------------------------
Bug #15406: Loaded iseq may cause SEGV on GC
https://bugs.ruby-lang.org/issues/15406#change-75639

* Author: wanabe (_ wanabe)
* Status: Closed
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: ruby 2.6.0dev (2018-12-13 trunk 66370) [x86_64-linux]
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN
----------------------------------------
Attached `test.rb` causes SEGV on trunk r66370.
`test.log` is stderr log.

I don't known what `[0, 13, 0]` means, but I guess environment dependent.
`./miniruby test.rb 4 17 0` also causes SEGV on mn environment but `./miniruby test.rb 4 16 0`  doesn't.

Note:
I've found the issue during the investigation of #15395, but I don't know it is related or not.

---Files--------------------------------
test.rb (282 Bytes)
test.log (10.5 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>