From: Greg.mpls@... Date: 2017-09-17T02:30:13+00:00 Subject: [ruby-core:82835] [Ruby trunk Bug#13910] Seg Fault from require_relative Issue #13910 has been reported by MSP-Greg (Greg L). ---------------------------------------- Bug #13910: Seg Fault from require_relative https://bugs.ruby-lang.org/issues/13910 * Author: MSP-Greg (Greg L) * Status: Open * Priority: Normal * 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 ---------------------------------------- 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](https://msp-greg.github.io/), 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 ```ruby raise(exception, string) ``` with ```ruby raise(string) ``` ---Files-------------------------------- loader.rb (115 Bytes) seg_fault.rb (1.31 KB) seg_fault.txt (4.42 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: