From: ko1@... Date: 2018-04-27T00:30:57+00:00 Subject: [ruby-core:86705] [Ruby trunk Bug#14607] Fix use of the rb_profile_frames start parameter Issue #14607 has been updated by ko1 (Koichi Sasada). I need to remember why such special (additional) calculation is done, so I left this ticket. I need to remember... ---------------------------------------- Bug #14607: Fix use of the rb_profile_frames start parameter https://bugs.ruby-lang.org/issues/14607#change-71663 * Author: dylants (Dylan Thacker-Smith) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: * 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. ---Files-------------------------------- fix-use-of-the-rb_profile_frames-start-parameter.patch (1.6 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: