From d676ad1050c0f570d6a2d1f983c1223611d45570 Mon Sep 17 00:00:00 2001 From: tenderlove Date: Thu, 26 Apr 2018 22:49:00 +0000 Subject: Fix use of `rb_profile_frames` start parameter 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. [ruby-core:86147] [Bug #14607] Co-authored-by: Dylan Thacker-Smith git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@63265 b2dd03c8-39d4-4d8f-98ff-823fe69b080e --- test/-ext-/debug/test_profile_frames.rb | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'test/-ext-/debug/test_profile_frames.rb') diff --git a/test/-ext-/debug/test_profile_frames.rb b/test/-ext-/debug/test_profile_frames.rb index 5ea506046e..672c9c4b5a 100644 --- a/test/-ext-/debug/test_profile_frames.rb +++ b/test/-ext-/debug/test_profile_frames.rb @@ -119,4 +119,8 @@ class TestProfileFrames < Test::Unit::TestCase a end; end + + def test_start + assert_equal Bug::Debug.profile_frames(0, 10).tap(&:shift), Bug::Debug.profile_frames(1, 9) + end end -- cgit v1.2.3