Issue #14607 has been updated by dylants (Dylan Thacker-Smith).
The original patch has a merge conflict. However, I have opened a pull request with the fix for this issue (https://github.com/ruby/ruby/pull/2713) that has been rebased to resolve the merge conflict.
The github PR has been merged, so this issue can be closed now. It doesn't look like I have permission to change its status though. ---------------------------------------- Bug #14607: Fix use of the rb_profile_frames start parameter https://bugs.ruby-lang.org/issues/14607#change-106253 * Author: dylants (Dylan Thacker-Smith) * Status: Assigned * Priority: Normal * Assignee: ko1 (Koichi Sasada) * Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN ---------------------------------------- rb_profile_frames was always behaving as if the value given for the start parameter was 0. The reason for this was that it would check `if (start > 0) {` then `continue` without updating the control frame pointer or anything other than decrementing `start`. This bug applies to all branches under normal maintenance, from ruby 2.3 to trunk. -- https://bugs.ruby-lang.org/