[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ruby-core
Subject:    [ruby-core:86704] [Ruby trunk Bug#14607][Open] Fix use of the rb_profile_frames start parameter
From:       tenderlove () ruby-lang ! org
Date:       2018-04-27 0:15:59
Message-ID: redmine.journal-71662.20180427001557.18dbdb23d020859b () ruby-lang ! org
[Download RAW message or body]

Issue #14607 has been updated by tenderlovemaking (Aaron Patterson).

Status changed from Closed to Open

ko1 said I shouldn't have committed the patch, so I reverted.  Sorry!

----------------------------------------
Bug #14607: Fix use of the rb_profile_frames start parameter
https://bugs.ruby-lang.org/issues/14607#change-71662

* 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: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>


[prev in list] [next in list] [prev in thread] [next in thread]