From: usa@...
Date: 2014-02-05T04:06:25+00:00
Subject: [ruby-core:60502] [ruby-trunk - Bug #9295] `Exception#backtrace_locations` returns `nil`

Issue #9295 has been updated by Usaku NAKAMURA.

Backport changed from 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN to 1.9.3: DONTNEED, 2.0.0: DONTNEED, 2.1: UNKNOWN

----------------------------------------
Bug #9295: `Exception#backtrace_locations` returns `nil`
https://bugs.ruby-lang.org/issues/9295#change-44967

* Author: Tsuyoshi Sawada
* Status: Closed
* Priority: High
* Assignee: 
* Category: 
* Target version: 
* ruby -v: 2.1
* Backport: 1.9.3: DONTNEED, 2.0.0: DONTNEED, 2.1: UNKNOWN
----------------------------------------
=begin
If I raise an `ArgumentError` by calling a method with wrong number of arguments, `Exception#backtrace_locations` returns `nil`, which I think is a bug:

    def foo; end

    begin
      foo(:bar)
    rescue => e
      p e.backtrace_locations
    end
    # => nil

If, instead, I raise an error manually, then it returns an array as expected:

    begin
      raise ArgumentError.new
    rescue => e
      p e.backtrace_locations
    end
    # => ["this_file:2:in `<main>'"]

=end



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