https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112013-12-06T12:03:41ZRuby Issue Tracking SystemRuby master - Bug #8860: 64-bit x86 ruby 1.9.3-p448 on Solaris core dumps on bug4950 test casehttps://bugs.ruby-lang.org/issues/8860?journal_id=434432013-12-06T12:03:41Zhsbt (Hiroshi SHIBATA)hsbt@ruby-lang.org
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Feedback</i></li></ul><p>Could you try latest version of Ruby 1.9.3?</p> Ruby master - Bug #8860: 64-bit x86 ruby 1.9.3-p448 on Solaris core dumps on bug4950 test casehttps://bugs.ruby-lang.org/issues/8860?journal_id=457032014-03-09T13:14:13Zyann (Yann Rouillard)yann@pleiades.fr.eu.org
<ul><li><strong>File</strong> <a href="/attachments/4292">core.part1</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/4292/core.part1">core.part1</a> added</li><li><strong>File</strong> <a href="/attachments/4293">core.part2</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/4293/core.part2">core.part2</a> added</li><li><strong>File</strong> <a href="/attachments/4294">test_fork_modified.rb</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/4294/test_fork_modified.rb">test_fork_modified.rb</a> added</li></ul><p>Hi,</p>
<p>I confirm that this bug is still present with ruby 1.9.3 patch level 484:<br>
Output of ruby -v: ruby 1.9.3p484 (2013-11-22 revision 43786) [i386-solaris2.10]</p>
<p>I attached the core dump (which is 6 MB, so it is split in two files) and you will find the stacktrace below.</p>
<p>I noticed that the core dump happens only if the two signals INT and TERM are sent, when I remove one line or the other, the core dump doesn't happen.</p>
<p>It also doesn't happen if I insert a 0.5s pause between the two signal (see the attached file test_forks_modified.rb).</p>
<p>I will try the last ruby 1.9.3 version that went out recently.</p>
<p>Stacktrace:</p>
<p>core 'core' of 12295: ./work/solaris10-i386/build-isa-pentium_pro/ruby-1.9.3-p484/ruby191 te<br>
----------------- lwp# 1 / thread# 1 --------------------<br>
feef8e29 __lwp_park (8061084, 80610b0, 8046020) + 19<br>
feef361b cond_wait_queue (8061084, 80610b0, 8046020) + 5e<br>
feef3998 cond_wait_common (8061084, 80610b0, 8046020) + 1db<br>
feef3bca _cond_timedwait (8061084, 80610b0, 80460d8) + 51<br>
feef3c35 cond_timedwait (8061084, 80610b0, 80460d8) + 24<br>
feef3c71 pthread_cond_timedwait (8061084, 80610b0, 80460d8, fed9a3de) + 1e<br>
fed9a3fe native_cond_timedwait (8061084, 80610b0, 80460d8, 0) + 2e<br>
fed9aa87 native_sleep (8061030, 8046154, feffa320, fed9c211) + d7<br>
fed9c26f sleep_timeval (8061030, 1, 0, fed9c41c) + 6c<br>
fed9c43a rb_thread_wait_for (1, 0, 0, fecc530d) + 2a<br>
fecc534f rb_f_sleep (1, 806525c, 8114da8, fed576b2) + 4f<br>
fed74d8d vm_exec_core (8061030, 0, fee2c4e0, fed97041) + 1d6ec<br>
fed9772e vm_exec (8061030, 80fe1c0, fef60018, fed9782d) + 6fe<br>
fed97852 rb_iseq_eval_main (80fe1c0, 8047a88, feef6b6a, fec5a101) + 32<br>
fec5a184 ruby_exec_internal (80fe1c0, 0, 0, fec5a27c, 8047b38) + 8f<br>
fec5a29a ruby_exec_node (80fe1c0) + 2a<br>
fec5a24b ruby_run_node (80fe1c0, 8047b98, 8047b68, 8050b78, 29, fef77790) + 34<br>
08050b8f main (2, 8047b98, 8047ba4, 8047b8c) + 5f<br>
08050a9d _start (2, 8047c5c, 8047ca0, 0, 8047cad, 8047d6d) + 7d<br>
----------------- lwp# 3 / thread# 3 --------------------<br>
feefde86 __systemcall (3, fee30618, 0) + 6<br>
feeeeb44 call_user_handler (2, fee30bdc, fee3068c) + 1e0<br>
feeeecd0 sigacthandler (2, fee30bdc, fee3068c) + 7c<br>
--- called from signal handler with signal 2 (SIGINT) ---<br>
feefbe95 __pollsys (fee32ca0, 1, 0, 0) + 15<br>
feea5871 pselect_large_fdset (4, fee32f40, fee30ca0, fee30ca0, 0, 0) + 1fd<br>
feea5b97 select_large_fdset (4, fee32f40, 0, 0, 0, 0) + 82<br>
fed9af1d thread_timer (8060dbc) + c5<br>
feef8aab _thr_setup (feba0200) + 4e<br>
feef8db0 _lwp_start (feba0200, 0, 0, fee32ff8, feef8db0, feba0200)</p> Ruby master - Bug #8860: 64-bit x86 ruby 1.9.3-p448 on Solaris core dumps on bug4950 test casehttps://bugs.ruby-lang.org/issues/8860?journal_id=457052014-03-09T13:35:15Zhsbt (Hiroshi SHIBATA)hsbt@ruby-lang.org
<ul><li><strong>Assignee</strong> set to <i>ngoto (Naohisa Goto)</i></li></ul> Ruby master - Bug #8860: 64-bit x86 ruby 1.9.3-p448 on Solaris core dumps on bug4950 test casehttps://bugs.ruby-lang.org/issues/8860?journal_id=457192014-03-11T05:23:46Zngoto (Naohisa Goto)ngotogenome@gmail.com
<ul></ul><p>The latest version is Ruby 1.9.3-p545. Please try the latest version.<br>
<a href="https://www.ruby-lang.org/en/news/2014/02/24/ruby-1-9-3-p545-is-released/" class="external">https://www.ruby-lang.org/en/news/2014/02/24/ruby-1-9-3-p545-is-released/</a></p>
<p>Could you try latest version of SolarisStudio 12.3 compiler?</p>
<p>I only use Solaris 10 on Sparc, and I don't have x86 Solaris. So, it is very hard to solve the problem.</p> Ruby master - Bug #8860: 64-bit x86 ruby 1.9.3-p448 on Solaris core dumps on bug4950 test casehttps://bugs.ruby-lang.org/issues/8860?journal_id=555472015-12-15T05:24:38Zngoto (Naohisa Goto)ngotogenome@gmail.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Closed</i></li></ul><p>Closed because of no feedback, and because 1.9.3 is EOL.</p>
<p>Recently, some problems about fork and exec on Solaris have been fixed.<br>
See [Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: deadlock on Solaris 10 since r50900 (Closed)" href="https://bugs.ruby-lang.org/issues/11265">#11265</a>], [Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: TestProcess#test_exec_fd_3_redirect failed on Solaris 10 (Closed)" href="https://bugs.ruby-lang.org/issues/11336">#11336</a>], and [Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: ASYNC BUG after failure of Process.exec when closing FD 3 (or 4 or 5) (Closed)" href="https://bugs.ruby-lang.org/issues/11353">#11353</a>], though these may not be related with this issue.</p>