[#60404] is RB_GC_GUARD needed in rb_io_syswrite? — Eric Wong <normalperson@...>
I haven't gotten it to crash as-is, but it seems like we need to
4 messages
2014/02/01
[#60682] volatile usages — Eric Wong <normalperson@...>
Hi all, I went ahead and removed some use of volatile which were once
5 messages
2014/02/13
[#60794] [RFC] rearrange+pack vtm and time_object structs — Eric Wong <normalperson@...>
Extracted from addendum on top of Feature #9362 (cache-aligned objects).
4 messages
2014/02/16
[#61139] [ruby-trunk - Feature #9577] [Open] [PATCH] benchmark/driver.rb: align columns in text output — normalperson@...
Issue #9577 has been reported by Eric Wong.
3 messages
2014/02/28
[ruby-core:60502] [ruby-trunk - Bug #9295] `Exception#backtrace_locations` returns `nil`
From:
usa@...
Date:
2014-02-05 04:06:25 UTC
List:
ruby-core #60502
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/