Bug #13910: Seg Fault from require_relative

• Status: Rejected
• Assignee: -
• Target version: -
• ruby -v: ruby 2.5.0dev (2017-09-14 trunk 59897) [x64-mingw32]
• Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN

[MSP-Greg (Greg L)]

As some of you may recall, I have been building MinGW trunk for several months. I have been logging the test results since April on my doc site, which has several versions of ruby and a few gems.

I mention this because I use the trunk builds to update the site, usually daily.

For the second time recently, running the site update code generated a seg fault. Info is attached as seg_fault.txt.

Attached are two rb files, place in the same folder, cd to the folder, and run:

ruby --disable-gems loader.rb

I tested several builds; the seg fault starts somewhere after svn 59870 and no later than svn 59897. Same results without --disable-gems, just added to shorten the seg fault info.

2017-09-09 59792  Okay
2017-09-11 59839  Okay
2017-09-14 59870  Okay

2017-09-14 59897  Fails
2017-09-16 59930  Fails

I removed as much content from seg_fault.rb as I could. I got to the point where I couldn't find any more lines that could be commented out and still generate the seg fault. For my code, I replaced

raise(exception, string)

with

raise(string)

[MSP-Greg (Greg L)]

Problem fixed. I assume Nobu's work has taken care of this. Thank you again.

2017-09-17_59946 Fails
2017-09-18_59956 Passes
2017-09-19_59967 Passes

I'm okay to close.

[hsbt (Hiroshi SHIBATA)]

• Status changed from Open to Rejected