https://redmine.ruby-lang.org/https://redmine.ruby-lang.org/favicon.ico?17113305112012-02-11T09:02:40ZRuby Issue Tracking SystemBackport193 - Backport #6000: respond_to? check in check_funcall() does not work with single-argument respond_to?https://redmine.ruby-lang.org/issues/6000?journal_id=237182012-02-11T09:02:40Zdrbrain (Eric Hodel)drbrain@segment7.net
<ul><li><strong>File</strong> <a href="/attachments/2450">vm_eval.c.respond_to_arity.patch</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2450/vm_eval.c.respond_to_arity.patch">vm_eval.c.respond_to_arity.patch</a> added</li></ul> Backport193 - Backport #6000: respond_to? check in check_funcall() does not work with single-argument respond_to?https://redmine.ruby-lang.org/issues/6000?journal_id=237232012-02-11T10:15:16Znobu (Nobuyoshi Nakada)nobu@ruby-lang.org
<ul></ul><p>seems fine.</p> Backport193 - Backport #6000: respond_to? check in check_funcall() does not work with single-argument respond_to?https://redmine.ruby-lang.org/issues/6000?journal_id=237302012-02-12T04:15:38Zdrbrain (Eric Hodel)drbrain@segment7.net
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>This issue was solved with changeset r34564.<br>
Eric, thank you for reporting this issue.<br>
Your contribution to Ruby is greatly appreciated.<br>
May Ruby be with you.</p>
<hr>
<ul>
<li>vm_eval.c (check_funcall): Call respond_to? with matching arity for<br>
legacy single-argument implementations. [ruby-trunk - Bug <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Backport: respond_to? check in check_funcall() does not work with single-argument respond_to? (Closed)" href="https://redmine.ruby-lang.org/issues/6000">#6000</a>]</li>
</ul> Backport193 - Backport #6000: respond_to? check in check_funcall() does not work with single-argument respond_to?https://redmine.ruby-lang.org/issues/6000?journal_id=238142012-02-14T11:35:25Znaruse (Yui NARUSE)naruse@airemix.jp
<ul><li><strong>Tracker</strong> changed from <i>Bug</i> to <i>Backport</i></li><li><strong>Project</strong> changed from <i>Ruby master</i> to <i>Backport193</i></li><li><strong>Category</strong> deleted (<del><i>core</i></del>)</li><li><strong>Status</strong> changed from <i>Closed</i> to <i>Open</i></li><li><strong>Target version</strong> deleted (<del><i>2.0.0</i></del>)</li></ul> Backport193 - Backport #6000: respond_to? check in check_funcall() does not work with single-argument respond_to?https://redmine.ruby-lang.org/issues/6000?journal_id=238782012-02-15T10:34:01Znobu (Nobuyoshi Nakada)nobu@ruby-lang.org
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul><p>This issue was solved with changeset r34616.<br>
Eric, thank you for reporting this issue.<br>
Your contribution to Ruby is greatly appreciated.<br>
May Ruby be with you.</p>
<hr>
<p>merge revision(s) r34564:</p>
<pre><code>* vm_eval.c (check_funcall): Call respond_to? with matching arity for
legacy single-argument implementations. [ruby-trunk - Bug #6000]
</code></pre> Backport193 - Backport #6000: respond_to? check in check_funcall() does not work with single-argument respond_to?https://redmine.ruby-lang.org/issues/6000?journal_id=245742012-03-14T19:51:47Zmame (Yusuke Endoh)mame@ruby-lang.org
<ul><li><strong>Status</strong> changed from <i>Closed</i> to <i>Assigned</i></li><li><strong>Assignee</strong> set to <i>drbrain (Eric Hodel)</i></li></ul><p>Hello,</p>
<p>Your patch causes SEGV:</p>
<p>class C<br>
def respond_to? x, y, z<br>
p z<br>
end<br>
end<br>
[C.new].flatten #=> SEGV</p>
<p>Did you mean "arity >= 3" instead of "arity > 3" ?<br>
(Note that I don't understand this ticket.)</p>
<p>Coverity Scan found this bug.</p>
<p>--<br>
Yusuke Endoh <a href="mailto:mame@tsg.ne.jp" class="email">mame@tsg.ne.jp</a></p> Backport193 - Backport #6000: respond_to? check in check_funcall() does not work with single-argument respond_to?https://redmine.ruby-lang.org/issues/6000?journal_id=245752012-03-14T20:16:24Zusa (Usaku NAKAMURA)usa@garbagecollect.jp
<ul><li><strong>Tracker</strong> changed from <i>Backport</i> to <i>Bug</i></li><li><strong>Project</strong> changed from <i>Backport193</i> to <i>Ruby master</i></li></ul> Backport193 - Backport #6000: respond_to? check in check_funcall() does not work with single-argument respond_to?https://redmine.ruby-lang.org/issues/6000?journal_id=245872012-03-15T07:23:18Zdrbrain (Eric Hodel)drbrain@segment7.net
<ul><li><strong>ruby -v</strong> set to <i>-</i></li></ul><p>=begin<br>
Fixed by r35025</p>
<p>I was depending upon vm_call0() to perform arity checking, but it does not, so r35025 does it by hand.</p>
<p>Existing ruby libraries have (({def respond_to? method})). Before r34564 ruby trunk called respond_to? with two arguments, the method and a boolean to include private methods, which broke backwards compatibility. This bug is about allowing respond_to? implementations from ruby 1.8 and ruby 1.9 to continue to work.<br>
=end</p> Backport193 - Backport #6000: respond_to? check in check_funcall() does not work with single-argument respond_to?https://redmine.ruby-lang.org/issues/6000?journal_id=245882012-03-15T07:25:29Zdrbrain (Eric Hodel)drbrain@segment7.net
<ul><li><strong>Status</strong> changed from <i>Assigned</i> to <i>Closed</i></li></ul><p>I do not know how to move this ticket to the Backport tracker, can someone please backport it?</p> Backport193 - Backport #6000: respond_to? check in check_funcall() does not work with single-argument respond_to?https://redmine.ruby-lang.org/issues/6000?journal_id=245892012-03-15T09:42:10Zmarcandre (Marc-Andre Lafortune)marcandre-ruby-core@marc-andre.ca
<ul><li><strong>Tracker</strong> changed from <i>Bug</i> to <i>Backport</i></li><li><strong>Project</strong> changed from <i>Ruby master</i> to <i>Backport193</i></li></ul><p>Moved as backport</p>