Bug #13910
closedSeg Fault from require_relative
Description
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)
Files