[#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:35045] Re: [Ruby 1.9-Bug#4352] [patch] Fix eval(s, b) backtrace; make eval(s, b) consistent with eval(s)

From: Yusuke ENDOH <mame@...>
Date: 2011-02-02 15:47:51 UTC
List: ruby-core #35045
Hi,

2011/2/2 James M. Lawrence <redmine@ruby-lang.org>:
> Thank you for that detailed explanation. The problem for me is the
> connection to source_location, which should be usable by tools.

What kind of tools are you talking about?
Even if a binding location is discarded, we can still fake __FILE__
and __LINE__ without using a binding:

  eval <<-END, nil, "/etc/passwd", 1
    def foo
    end
  END
  p method(:foo).source_location  #=> ["/etc/passwd", 1]

So, source_location user should know and accept the fact that the
information is not trustable.
Why do you think only a binding location as a problem?

-- 
Yusuke Endoh <mame@tsg.ne.jp>

In This Thread