Bug #15604: Backport r66349 to 2.5

• Status: Closed
• Assignee: -
• Target version: -
• ruby -v: 2.5.3
• Backport: 2.4: UNKNOWN, 2.5: REQUIRED, 2.6: DONTNEED

[rafaelfranca (Rafael França)]

Revision r66349 fixes a bug that was causing byebug to not reliable work if your code was using Fowardable.

See also https://bugs.ruby-lang.org/issues/15303

[shyouhei (Shyouhei Urabe)]

• Status changed from Open to Closed

(Changing status to closed, which would trigger the backporting process. Don't take it as a rejection.)

[rafaelfranca (Rafael França)]

Thank you! Do you need to change the backport field to point it needs to be backported to 2.5 but not to 2.6?

[shyouhei (Shyouhei Urabe)]

rafaelfranca (Rafael França) wrote:

Thank you! Do you need to change the backport field to point it needs to be backported to 2.5 but not to 2.6?

Thank you. But leaving that field UNKNOWN is just OK.

[nagachika (Tomoyuki Chikanaga)]

• Is duplicate of Bug #15303: Return tracepoint doesn't fire when tailcall optimization is applied added

[nagachika (Tomoyuki Chikanaga)]

• Backport changed from 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN to 2.4: UNKNOWN, 2.5: REQUIRED, 2.6: DONTNEED