From: Motohiro KOSAKI <kosaki.motohiro@...>
Date: 2011-07-21T20:43:57+09:00
Subject: [ruby-core:38328] [Ruby 1.9 - Feature #4347] Tracing cannot be re-enabled after callcc [patch]


Issue #4347 has been updated by Motohiro KOSAKI.

Assignee changed from Motohiro KOSAKI to Yusuke Endoh

> @James
> Sorry, I didn't make the deadline to import your patch.
> Kosaki, who is the "virtual" release manager, changed this ticket to
> 1.9.x feature.
> I've just imported it to trunk.  It is up to a release manager to
> decide whether this is imported to 1.9.3 or not.

Of course, I'd respect your decision. Please commit it to ruby_1_9_3 branch. ;-)

----------------------------------------
Feature #4347: Tracing cannot be re-enabled after callcc [patch]
http://redmine.ruby-lang.org/issues/4347

Author: James M. Lawrence
Status: Assigned
Priority: Normal
Assignee: Yusuke Endoh
Category: core
Target version: 1.9.x


=begin
 % patch -p1 < test_continuation_tracing.patch 
 patching file test/ruby/test_continuation.rb
 % ./ruby -v test/ruby/test_continuation.rb 
 ruby 1.9.3dev (2011-01-30 trunk 30735) [i386-darwin9.8.0]
 Run options: 
 
 # Running tests:
 
 ......FF
 
 Finished tests in 0.080788s, 99.0246 tests/s, 148.5369 assertions/s.
 
   1) Failure:
 test_tracing_with_set_trace_func(TestContinuation) [test/ruby/test_continuation.rb:99]:
 <3> expected but was
 <1>.
 
   2) Failure:
 test_tracing_with_thread_set_trace_func(TestContinuation) [test/ruby/test_continuation.rb:121]:
 <3> expected but was
 <0>.
 
 In thread.c (thread_suppress_tracing) the code after (*func)(arg, running)
 is not executed, causing th->tracing to not be cleared.
 
 This two-line patch works, though it may only address a symptom.
=end



-- 
http://redmine.ruby-lang.org