Bug #6535

[MinGW] Unexpected close program dialog for TestRubyOptions#test_segv_test

Added by Luis Lavena about 3 years ago. Updated about 3 years ago.

[ruby-core:45389]
Status:Closed
Priority:Normal
Assignee:Nobuyoshi Nakada
ruby -v:ruby 2.0.0dev (2012-06-02 trunk 35867) [i386-mingw32] Backport:

Description

=begin
Hello,

While running tests for MinGW-based build of trunk, I've found the mentioned test (test_segv_test) always blocks test execution.

The command issue to trigger this was:

make test-all TESTS="-q -v ruby/test_rubyoptions.rb -n test_segv_test"

Which triggers a Windows dialog indicating the failure (see attached)

And the following backtrace:

test_segv_test(TestRubyOptions):
IOError: stream closed
C:/Users/Worker/Code/ruby/ruby/test/ruby/envutil.rb:60:in read'
C:/Users/Worker/Code/ruby/ruby/test/ruby/envutil.rb:60:in
block in invoke_ruby'

1 tests, 0 assertions, 0 failures, 1 errors, 0 skips

Is this issue also showing on mswin builds? This seems to be a blocker for running continuous integration tests as the crash dialog needs to be closed manually.

Thank you.

=end

crash.png (15.6 KB) Luis Lavena, 06/03/2012 01:28 AM


Related issues

Related to Backport193 - Backport #6640: Backport fixes for [ruby-core:45389]: [MinGW] Unexpected close program dialog for TestRubyOptions#test_segv_test Closed 06/25/2012

Associated revisions

Revision 35913
Added by Nobuyoshi Nakada about 3 years ago

no windows dialog

  • win32/win32.c (rb_w32_sysinit): let the system not display the critical-error-handler message box and the Windows Error Reporting dialog. [Bug #6535]

Revision 35913
Added by Nobuyoshi Nakada about 3 years ago

no windows dialog

  • win32/win32.c (rb_w32_sysinit): let the system not display the critical-error-handler message box and the Windows Error Reporting dialog. [Bug #6535]

History

#1 Updated by Hiroshi Shirosaki about 3 years ago

I saw similar blocking issues with the following tests while MinGW test-all, but mswin build doesn't have.

test_segv_test in ruby/test_rubyoptions.rb
test_require_invalid_shared_object in ruby/test_require.rb.
test_separate in test/testunit/test_parallel.rb

Modifying registry value as below works fine for me on Win7.

http://support.microsoft.com/kb/124873/en-us

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows\ErrorMode
Modify ErrorMode value to 2.

The following command will complete with mingw build.
make test-all TESTS="-qv -j2"

#2 Updated by Usaku NAKAMURA about 3 years ago

  • Assignee changed from Usaku NAKAMURA to Nobuyoshi Nakada

So, this is mingw issue, I guess.

#3 Updated by Nobuyoshi Nakada about 3 years ago

  • Status changed from Assigned to Closed
  • % Done changed from 0 to 100

This issue was solved with changeset r35913.
Luis, thank you for reporting this issue.
Your contribution to Ruby is greatly appreciated.
May Ruby be with you.


no windows dialog

  • win32/win32.c (rb_w32_sysinit): let the system not display the critical-error-handler message box and the Windows Error Reporting dialog. [Bug #6535]

Also available in: Atom PDF