From: Greg.mpls@... Date: 2017-03-07T04:58:40+00:00 Subject: [ruby-core:79948] [Ruby trunk Bug#13288] mingw issues with 57789 Issue #13288 has been updated by Greg L. Shyouhei Urabe wrote: > While I was investigating this issue, naruse reverted some part of the commit nonetheless. I hate it when that happens... > Can you pull the latest trunk and see if the problem still exists? Started. About that previous question - does having info on both x86_64 and i686 help, or, dependent on the issue? ---------------------------------------- Bug #13288: mingw issues with 57789 https://bugs.ruby-lang.org/issues/13288#change-63372 * Author: Greg L * Status: Assigned * Priority: Normal * Assignee: Shyouhei Urabe * Target version: * ruby -v: ruby 2.5.0dev (2017-03-06 trunk 57789) [x64-mingw32] * Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN ---------------------------------------- I have been building trunk with mingw/MSYS2 for a few months. I also created packages using OpenSSL 1.1.0e and gdbm 1.10. Yesterday, I build 57782 with no major issues. Today, when I built 57789 (this commit) I had a segfault in the test-all section. the build.log was fine, and it responds to ruby -v, but I haven't tested further. I built 57782 and 57788 with no major issues. I built 57789 again, and again, the segfault occurred. The full log is at [x86_64-check.log](https://github.com/MSP-Greg/ruby-makepkg-mingw/blob/master/ruby_seg_fault/x86_64-check.log), also attached. I'm not a c type, so if there's anything else you need or would like me to check, please let me know. ---Files-------------------------------- x86_64-check.log (75 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: