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

From: "James M. Lawrence" <redmine@...>
Date: 2011-02-02 05:36:09 UTC
List: ruby-core #35041
Issue #4352 has been updated by James M. Lawrence.


Thank you for that detailed explanation. The problem for me is the
connection to source_location, which should be usable by tools.

Shouldn't source_location give the file and line of a method or block
definition? If so then source_location is bugged when the binding
argument is passed.

The seemingly simplest solution is to make the backtrace and
source_location consistent. It only takes a 4-line patch.

I might have thought otherwise if virtual line numbers served some
human purpose, but I just see them as confusing. Tools are even more
confused.

Should a new bug for source_location be created?
----------------------------------------
http://redmine.ruby-lang.org/issues/show/4352

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

In This Thread