[#86520] [Ruby trunk Bug#14681] `syswrite': stream closed in another thread (IOError) — samuel@...
Issue #14681 has been reported by ioquatix (Samuel Williams).
3 messages
2018/04/12
[#86755] [Ruby trunk Feature#14723] [WIP] sleepy GC — normalperson@...
Issue #14723 has been reported by normalperson (Eric Wong).
6 messages
2018/04/29
[ruby-core:86704] [Ruby trunk Bug#14607][Open] Fix use of the rb_profile_frames start parameter
From:
tenderlove@...
Date:
2018-04-27 00:15:59 UTC
List:
ruby-core #86704
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>