https://redmine.ruby-lang.org/https://redmine.ruby-lang.org/favicon.ico?17113305112009-08-01T23:35:31ZRuby Issue Tracking SystemBackport191 - Bug #1856: [BUG] Segmentation fault in 1.9.1p149https://redmine.ruby-lang.org/issues/1856?journal_id=50472009-08-01T23:35:31Zanthonywright (Anthony Wright)anthony@overnetdata.com
<ul></ul><p>=begin<br>
Oops, I think I'm finding bugs in versions that haven't even been released yet! As I said elsewhere in the post I meant 1.9.1p129...<br>
=end</p> Backport191 - Bug #1856: [BUG] Segmentation fault in 1.9.1p149https://redmine.ruby-lang.org/issues/1856?journal_id=50482009-08-01T23:38:50Zrogerdpack (Roger Pack)rogerpack2005@gmail.com
<ul></ul><p>=begin<br>
have you tried it with ruby trunk?<br>
=end</p> Backport191 - Bug #1856: [BUG] Segmentation fault in 1.9.1p149https://redmine.ruby-lang.org/issues/1856?journal_id=50492009-08-02T00:09:50Zphasis68 (Heesob Park)phasis@gmail.com
<ul></ul><p>=begin<br>
I think this segmentation fault is due to the bug of your code.</p>
<h2>Here is a patch for your code seg-fault.rb:<br>
@@ -42,7 +42,7 @@<br>
rd[1].close ; STDIN .reopen(rd[0]) ; rd[0].close<br>
wr[0].close ; STDOUT.reopen(wr[1]) ; wr[1].close<br>
err[0].close ; STDERR.reopen(err[1]) ; err[1].close</h2>
<ul>
<li>
<pre><code> ps[0].close
begin
exec(*cmd)
raise "exec returned!"
</code></pre>
</li>
</ul>
<h2>@@ -66,7 +66,7 @@<br>
rescue EOFError<br>
# If we get an EOF error, then the exec was successful.<br>
end</h2>
<ul>
<li>ps[0].close
<a name="If-exc-is-set-then-the-exec-was-NOT-successful"></a>
<h1 >If exc is set, then the exec was NOT successful.<a href="#If-exc-is-set-then-the-exec-was-NOT-successful" class="wiki-anchor">¶</a></h1>
if not exc.nil? then<br>
raise exc</li>
</ul>
<p>=end</p> Backport191 - Bug #1856: [BUG] Segmentation fault in 1.9.1p149https://redmine.ruby-lang.org/issues/1856?journal_id=100322010-04-10T11:54:38Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Feedback</i></li></ul><p>=begin<br>
Hi,</p>
<p>2009/8/1 Anthony Wright <a href="mailto:redmine@ruby-lang.org" class="email">redmine@ruby-lang.org</a>:</p>
<blockquote>
<p>I have a 120 line pure ruby application that bombs out in 1.9.1p129 after 1-2 seconds with a [BUG] Segmentation fault & [BUG] object allocation during garbage collection phase.</p>
<p>I'm using a piece of code that I got from Ruby Treasures which has worked fine in 1.8.X for a long time. I'm going through the process of porting to 1.9.1. I've inlined this code, and my little app that uses it is at the bottom.</p>
</blockquote>
<p>Thank you for report.<br>
But I cannot reproduce with both ruby 1.9.1p129 and trunk.<br>
Can anyone reproduce?</p>
<p>I guess this bug may depend on gcc's optimization.<br>
Could you tell us how did you build ruby?</p>
<p>--<br>
Yusuke ENDOH <a href="mailto:mame@tsg.ne.jp" class="email">mame@tsg.ne.jp</a><br>
=end</p> Backport191 - Bug #1856: [BUG] Segmentation fault in 1.9.1p149https://redmine.ruby-lang.org/issues/1856?journal_id=811552019-08-27T16:47:47Zjeremyevans0 (Jeremy Evans)merch-redmine@jeremyevans.net
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/81155/diff?detail_id=54818">diff</a>)</li><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Closed</i></li></ul>