From: Greg.mpls@... Date: 2017-10-24T16:38:23+00:00 Subject: [ruby-core:83545] [Ruby trunk Bug#14049] SEGV svn 60401 require_relative Issue #14049 has been reported by MSP-Greg (Greg L). ---------------------------------------- Bug #14049: SEGV svn 60401 require_relative https://bugs.ruby-lang.org/issues/14049 * Author: MSP-Greg (Greg L) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.5.0dev (2017-10-24 trunk 60401) [x64-mingw32] SEGV fault * Backport: 2.3: UNKNOWN, 2.4: UNKNOWN ---------------------------------------- Once again, MinGW builds are passing `test-all`, but I'm having issues when running the code for my [doc site](https://msp-greg.github.io/). I've got a SEGV in an rb file that starts with several `require_relative` commands. I haven't tried to isolate it, but if that would be helpful, please let me know. SEGV log files attached. ``` ruby 2.5.0dev (2017-10-24 trunk 60388) [x64-mingw32] NO fault, works fine ruby 2.5.0dev (2017-10-24 trunk 60401) [x64-mingw32] SEGV fault ruby 2.5.0dev (2017-10-24 trunk 60403) [x64-mingw32] SEGV fault ``` It's odd, because (from commit comments) I assume these changes are due to the recent running failures in the Appveyor mswin build. During that time, MinGW trunk builds were still passing tests and working with my doc site update code. But, `test-all` was running slower, and also showing fewer assertions. Table of results [here](https://msp-greg.github.io/file.mingw_test-all.html). Thanks, and thanks to everyone who contributed this weekend, Greg ---Files-------------------------------- SEGV_60403.txt (26.4 KB) SEGV_60401.txt (26.4 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: