From: alxtskrnk@...
Date: 2017-03-16T18:31:30+00:00
Subject: [ruby-core:80190] [Ruby trunk Bug#13320] rescue blocks get an entry in backtrace locations

Issue #13320 has been reported by bughit (bug hit).

----------------------------------------
Bug #13320: rescue blocks get an entry in backtrace locations
https://bugs.ruby-lang.org/issues/13320

* Author: bughit (bug hit)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: ruby 2.4.0p0 (2016-12-24 revision 57164) [x86_64-linux]
* Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN
----------------------------------------
```ruby
def foo
  puts caller(0)
end

def bar
  raise
rescue
  foo
end

bar
```

foo
rescue in bar
bar

this does not seem to make sense, conceptually a rescue block is not a separate callable entity, but just a section of a method, why should it get its own entry in the call stack?



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>