https://bugs.ruby-lang.org/https://bugs.ruby-lang.org/favicon.ico?17113305112016-01-07T14:38:40ZRuby Issue Tracking SystemRuby master - Bug #11954: "self has wrong type to call super in this context" under weird circumstanceshttps://bugs.ruby-lang.org/issues/11954?journal_id=560102016-01-07T14:38:40Zsplattael (Peter Leitzen)
<ul></ul><p>I can reproduce this bug on 2.3.0 and was able to reduce the broken code even more increasing the amount of iterations:</p>
<p><a href="https://gist.github.com/splattael/7b45e0f16e0084f50668" class="external">https://gist.github.com/splattael/7b45e0f16e0084f50668</a></p> Ruby master - Bug #11954: "self has wrong type to call super in this context" under weird circumstanceshttps://bugs.ruby-lang.org/issues/11954?journal_id=560172016-01-08T01:48:15Zshugo (Shugo Maeda)
<ul><li><strong>File</strong> <a href="/attachments/5737">invoke_bmethod.diff</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/5737/invoke_bmethod.diff">invoke_bmethod.diff</a> added</li><li><strong>Status</strong> changed from <i>Open</i> to <i>Assigned</i></li><li><strong>Assignee</strong> set to <i>ko1 (Koichi Sasada)</i></li></ul><p>The bug was introduced in r52104 by ko1, and it seems to be fixed by the attached patch, but Im' not sure.</p> Ruby master - Bug #11954: "self has wrong type to call super in this context" under weird circumstanceshttps://bugs.ruby-lang.org/issues/11954?journal_id=580042016-04-11T06:21:35Zko1 (Koichi Sasada)
<ul></ul><p>Shugo-san, thank you for your investigating.<br>
It seems perfect.<br>
Could you commit it? or should I commit it?</p>
<p>Thanks,<br>
Koichi</p> Ruby master - Bug #11954: "self has wrong type to call super in this context" under weird circumstanceshttps://bugs.ruby-lang.org/issues/11954?journal_id=592212016-06-14T10:46:01Zfcheung (Frederick Cheung)frederick.cheung@gmail.com
<ul></ul><p>Koichi Sasada wrote:</p>
<blockquote>
<p>Shugo-san, thank you for your investigating.<br>
It seems perfect.<br>
Could you commit it? or should I commit it?</p>
</blockquote>
<p>Was this ever committed/backported ? I've encountered this in real world usage with 2.3.1, and Peter's reproduction script continues to show the issue (although I had to increase iteration count to get consistent failure)</p> Ruby master - Bug #11954: "self has wrong type to call super in this context" under weird circumstanceshttps://bugs.ruby-lang.org/issues/11954?journal_id=592812016-06-20T03:18:19Zshugo (Shugo Maeda)
<ul><li><strong>Assignee</strong> changed from <i>ko1 (Koichi Sasada)</i> to <i>shugo (Shugo Maeda)</i></li></ul><p>I missed ko1's comment. I'll commit it later.</p> Ruby master - Bug #11954: "self has wrong type to call super in this context" under weird circumstanceshttps://bugs.ruby-lang.org/issues/11954?journal_id=592822016-06-20T04:37:25Zshugo (Shugo Maeda)
<ul><li><strong>Status</strong> changed from <i>Assigned</i> to <i>Closed</i></li></ul><p>Applied in changeset r55462.</p>
<hr>
<ul>
<li>vm.c (invoke_bmethod, invoke_block_from_c_0): revert r52104<br>
partially to avoid "self has wrong type to call super in this<br>
context" errors.<br>
<a href="/issues/11954">[ruby-core:72724]</a> [Bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: "self has wrong type to call super in this context" under weird circumstances (Closed)" href="https://bugs.ruby-lang.org/issues/11954">#11954</a>]</li>
</ul> Ruby master - Bug #11954: "self has wrong type to call super in this context" under weird circumstanceshttps://bugs.ruby-lang.org/issues/11954?journal_id=592832016-06-20T04:40:10Zshugo (Shugo Maeda)
<ul><li><strong>Backport</strong> changed from <i>2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN</i> to <i>2.0.0: DONTNEED, 2.1: DONTNEED, 2.2: DONTNEED, 2.3: REQUIRED</i></li></ul> Ruby master - Bug #11954: "self has wrong type to call super in this context" under weird circumstanceshttps://bugs.ruby-lang.org/issues/11954?journal_id=594342016-07-01T18:59:10Znagachika (Tomoyuki Chikanaga)nagachika00@gmail.com
<ul><li><strong>Backport</strong> changed from <i>2.0.0: DONTNEED, 2.1: DONTNEED, 2.2: DONTNEED, 2.3: REQUIRED</i> to <i>2.0.0: DONTNEED, 2.1: DONTNEED, 2.2: DONTNEED, 2.3: DONE</i></li></ul><p>ruby_2_3 r55560 merged revision(s) 55462.</p>