[#35027] [Ruby 1.9-Bug#4352][Open] [patch] Fix eval(s, b) backtrace; make eval(s, b) consistent with eval(s) — "James M. Lawrence" <redmine@...>

Bug #4352: [patch] Fix eval(s, b) backtrace; make eval(s, b) consistent with eval(s)

16 messages 2011/02/01

[#35114] [Ruby 1.9-Bug#4373][Open] http.rb:677: [BUG] Segmentation fault — Christian Fazzini <redmine@...>

Bug #4373: http.rb:677: [BUG] Segmentation fault

59 messages 2011/02/06

[#35171] [Ruby 1.9-Bug#4386][Open] encoding: directive does not affect regex expressions — mathew murphy <redmine@...>

Bug #4386: encoding: directive does not affect regex expressions

9 messages 2011/02/09

[#35237] [Ruby 1.9-Bug#4400][Open] nested at_exit hooks run in strange order — Suraj Kurapati <redmine@...>

Bug #4400: nested at_exit hooks run in strange order

12 messages 2011/02/15

[ruby-core:35236] [Ruby 1.9-Bug#3660] Trace events seem to be missing

From: Rocky Bernstein <redmine@...>
Date: 2011-02-15 03:28:49 UTC
List: ruby-core #35236
Issue #3660 has been updated by Rocky Bernstein.


I don't think the problem is directly related to r24226. Instead, I think the call stack is one level one deeper than it had been previously due to the way "require" now works.

Around line 186 of lib/tracer.rb do the end:

if $0 == __FILE__
 ...
elsif caller.size <= 1 
  Tracer.on
end

But caller now reports: 

["<internal:lib/rubygems/custom_require>:29:in `require'", "<internal:lib/rubygems/custom_require>:29:in `require'"]

Changing the value in the "elsif" test from 1 to 2 will start showing trace output. However one may
want to do a more rigorous test and match on values in caller looking for <internal:lib/rubygems/custom_require> or something like that. 



----------------------------------------
http://redmine.ruby-lang.org/issues/show/3660

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

In This Thread