https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112012-02-10T17:49:09ZRuby Issue Tracking SystemRuby master - Bug #5931: Random SEGV during execution on YARD specshttps://bugs.ruby-lang.org/issues/5931?journal_id=236882012-02-10T17:49:09Znaruse (Yui NARUSE)naruse@airemix.jp
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Feedback</i></li></ul><p>Could you try trunk/latest 1.9.3?<br>
I doubt this is caused by the same reason of <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Backport: make check fails when compiling with GCC 4.7 - *** longjmp causes uninitialized stack frame *** (Closed)" href="https://bugs.ruby-lang.org/issues/5851">#5851</a>.</p> Ruby master - Bug #5931: Random SEGV during execution on YARD specshttps://bugs.ruby-lang.org/issues/5931?journal_id=237132012-02-11T05:48:01Zvo.x (Vit Ondruch)v.ondruch@tiscali.cz
<ul></ul><p>The patch fixing <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Backport: make check fails when compiling with GCC 4.7 - *** longjmp causes uninitialized stack frame *** (Closed)" href="https://bugs.ruby-lang.org/issues/5851">#5851</a> was applied, so that is definitely different issue. But yes, I can try it next week with trunk.</p> Ruby master - Bug #5931: Random SEGV during execution on YARD specshttps://bugs.ruby-lang.org/issues/5931?journal_id=240072012-02-21T18:49:56Zvo.x (Vit Ondruch)v.ondruch@tiscali.cz
<ul></ul><p>It crashed on 8th retry with ruby 1.9.3p125 (2012-02-16 revision 34643) [x86_64-linux]. Going to try with trunk ...</p> Ruby master - Bug #5931: Random SEGV during execution on YARD specshttps://bugs.ruby-lang.org/issues/5931?journal_id=240272012-02-22T16:53:45Zvo.x (Vit Ondruch)v.ondruch@tiscali.cz
<ul></ul><p>I gave it try with ruby 2.0.0dev (2012-02-21 trunk 34723) [x86_64-linux] and it does not segfaulted in 1000 runs. Now I'm wondering what was the fix, since I'd love to see it backported to Ruby 1.9.3.</p> Ruby master - Bug #5931: Random SEGV during execution on YARD specshttps://bugs.ruby-lang.org/issues/5931?journal_id=240302012-02-22T17:29:11Znormalperson (Eric Wong)normalperson@yhbt.net
<ul></ul><p>Vit Ondruch <a href="mailto:v.ondruch@tiscali.cz" class="email">v.ondruch@tiscali.cz</a> wrote:</p>
<blockquote>
<p>I gave it try with ruby 2.0.0dev (2012-02-21 trunk 34723)<br>
[x86_64-linux] and it does not segfaulted in 1000 runs. Now I'm<br>
wondering what was the fix, since I'd love to see it backported to<br>
Ruby 1.9.3.</p>
</blockquote>
<p>Perhaps it was the gc.c change in r34719?<br>
Can you revert that and see if you can reproduce the segfault?<br>
Perhaps you can confirm my suspicion from <a href="https://blade.ruby-lang.org/ruby-core/42794">[ruby-core:42794]</a></p> Ruby master - Bug #5931: Random SEGV during execution on YARD specshttps://bugs.ruby-lang.org/issues/5931?journal_id=240622012-02-23T20:24:27Zvo.x (Vit Ondruch)v.ondruch@tiscali.cz
<ul></ul><p>Eric Wong wrote:</p>
<blockquote>
<p>Vit Ondruch <a href="mailto:v.ondruch@tiscali.cz" class="email">v.ondruch@tiscali.cz</a> wrote:</p>
<blockquote>
<p>I gave it try with ruby 2.0.0dev (2012-02-21 trunk 34723)<br>
[x86_64-linux] and it does not segfaulted in 1000 runs. Now I'm<br>
wondering what was the fix, since I'd love to see it backported to<br>
Ruby 1.9.3.</p>
</blockquote>
<p>Perhaps it was the gc.c change in r34719?<br>
Can you revert that and see if you can reproduce the segfault?<br>
Perhaps you can confirm my suspicion from <a href="https://blade.ruby-lang.org/ruby-core/42794">[ruby-core:42794]</a></p>
</blockquote>
<p>Seems to be something different. It works (I gave it 160 tries) although I reverted the r34719.</p> Ruby master - Bug #5931: Random SEGV during execution on YARD specshttps://bugs.ruby-lang.org/issues/5931?journal_id=320922012-10-31T20:44:45Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Assigned</i></li><li><strong>Assignee</strong> set to <i>usa (Usaku NAKAMURA)</i></li></ul><p>Usa-san, please!</p>
<p>--<br>
Yusuke Endoh <a href="mailto:mame@tsg.ne.jp" class="email">mame@tsg.ne.jp</a></p> Ruby master - Bug #5931: Random SEGV during execution on YARD specshttps://bugs.ruby-lang.org/issues/5931?journal_id=674292017-10-21T11:50:02Zusa (Usaku NAKAMURA)usa@garbagecollect.jp
<ul><li><strong>Status</strong> changed from <i>Assigned</i> to <i>Rejected</i></li></ul><p>1.9 is out of date</p>