Issue #14049 has been updated by MSP-Greg (Greg L).


I did some more work with this.  The SEGV is happening from one particular file being loaded via `relative_require`, and although the SEGV log seems to indicate that as the 'last' function, the issue seems to be a parsing issue, which I've narrowed down to the statement, but I haven't reduced it to a simple test case.

Re `test-all` assertions and `test-all` time, as of `ruby 2.5.0dev (2017-10-26 trunk 60450) [x64-mingw32]`, test run times are lower than I've ever seen them.  But, the test and assertion counts have dropped, so I will investigate further.

To match up better with Travis and Appveyor mswin, I'm now running `test-all`, `test-spec`, and `mspec` parallel (`-j2` on `test-all`, `-j` on specs).

Also, the rolling [ruby-loco trunk build](https://ci.appveyor.com/project/MSP-Greg/ruby-loco/history) is now running three times a day at Noon, 6:00 P and 1:00 A JST.

Finally (with my limited *nix scripting skills) I created a companion to [appveyor-ruby](https://ci.appveyor.com/project/MSP-Greg/appveyor-ruby) on Travis, [travis-ruby](https://travis-ci.org/MSP-Greg/travis-ruby).  It shows info on default and available Ruby builds.  I created it mostly to see what library versions were used to compile the various version.  I'll update it manually as I notice changes.  Some interesting version differences:

```
           rvm      mingw    
GDBM      1.8.3     1.10
LIBYAML   0.1.4     0.1.7
OpenSSL   1.0.1f    1.1.0f
Readline  6.3       7.0
Zlib      1.2.8     1.2.11
```



Thanks again.  Some info might be helpful for people, otherwise, please close in a few days...

@shevegen - Thank you.  Someone has to do it.  I've been using and coding on Windows since DOS days, and in traditional corporate America, it's still the standard...



----------------------------------------
Bug #14049: SEGV svn 60401 require_relative
https://bugs.ruby-lang.org/issues/14049#change-67609

* 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: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>