[#83773] [Ruby trunk Bug#14108] Seg Fault with MinGW on svn 60769 — usa@...
Issue #14108 has been updated by usa (Usaku NAKAMURA).
9 messages
2017/11/15
[#83774] Re: [Ruby trunk Bug#14108] Seg Fault with MinGW on svn 60769
— Eric Wong <normalperson@...>
2017/11/15
usa@garbagecollect.jp wrote:
[#83775] Re: [Ruby trunk Bug#14108] Seg Fault with MinGW on svn 60769
— "U.NAKAMURA" <usa@...>
2017/11/15
Hi, Eric
[#83779] Re: [Ruby trunk Bug#14108] Seg Fault with MinGW on svn 60769
— Eric Wong <normalperson@...>
2017/11/15
"U.NAKAMURA" <usa@garbagecollect.jp> wrote:
[#83781] Re: [Ruby trunk Bug#14108] Seg Fault with MinGW on svn 60769
— "U.NAKAMURA" <usa@...>
2017/11/15
Hi, Eric,
[#83782] Re: [Ruby trunk Bug#14108] Seg Fault with MinGW on svn 60769
— Eric Wong <normalperson@...>
2017/11/15
"U.NAKAMURA" <usa@garbagecollect.jp> wrote:
[ruby-core:83635] [Ruby trunk Bug#14074] TracePoint#new without a block should not raise ThreadError
From:
atul1bhosale@...
Date:
2017-11-01 14:02:29 UTC
List:
ruby-core #83635
Issue #14074 has been updated by atul (Atul Bhosale). While working on RubySpecs with Marc-Andre Lafortune, we discovered that TracePoint.new raises a ThreadError instead of ArgumentError. For example : ~~~ ruby TracePoint.new => # => ThreadError: must be called with a block ~~~ ---------------------------------------- Bug #14074: TracePoint#new without a block should not raise ThreadError https://bugs.ruby-lang.org/issues/14074#change-67663 * Author: atul (Atul Bhosale) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: trunk * Backport: 2.3: UNKNOWN, 2.4: UNKNOWN ---------------------------------------- While working on RubySpecs with Marc-Andre Lafortune, we discovered that TracePoint.new raises a ThreadError instead of ArgumentError. For example : ~~~ ruby TracePoint.new => # => ThreadError: must be called with a block ~~~ -- 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>