Project

General

Profile

Bug #15604

Backport r66349 to 2.5

Added by rafaelfranca (Rafael França) 4 months ago. Updated 2 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
[ruby-core:91534]

Description

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


Related issues

Is duplicate of Ruby trunk - Bug #15303: Return tracepoint doesn't fire when tailcall optimization is appliedClosedActions

History

Updated by shyouhei (Shyouhei Urabe) 4 months ago

  • Status changed from Open to Closed

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

Updated by rafaelfranca (Rafael França) 4 months ago

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?

Updated by shyouhei (Shyouhei Urabe) 4 months ago

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.

#4

Updated by nagachika (Tomoyuki Chikanaga) 2 months ago

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

Updated by nagachika (Tomoyuki Chikanaga) 2 months ago

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

Also available in: Atom PDF