[MacRuby] #365: nil.setStringValue causes SIGABRT
#365: nil.setStringValue causes SIGABRT -------------------------------+-------------------------------------------- Reporter: cwdinfo@… | Owner: lsansonetti@… Type: defect | Status: new Priority: major | Milestone: Component: MacRuby | Keywords: 32-bit, SIGABRT -------------------------------+-------------------------------------------- Misusing an ivar that has not been set results in calling a method on a nil object. The attached code illustrates. More info in README. Observed on MBP 2.16 GHz Intel Core Duo OSX V.10.6.1 MacRuby version 0.5 (ruby 1.9.0) [universal-darwin10.0, i386] -- Ticket URL: <http://www.macruby.org/trac/ticket/365> MacRuby <http://macruby.org/>
#365: nil.setStringValue causes SIGABRT -------------------------------+-------------------------------------------- Reporter: cwdinfo@… | Owner: lsansonetti@… Type: defect | Status: new Priority: major | Milestone: Component: MacRuby | Keywords: 32-bit, SIGABRT -------------------------------+-------------------------------------------- Comment(by lsansonetti@…): This program crashes in 32-bit because currently Objective-C cannot intercept MacRuby exceptions. So, sending a message to nil triggers an exception which calls std::terminate() because there is no active handler. -- Ticket URL: <http://www.macruby.org/trac/ticket/365#comment:1> MacRuby <http://macruby.org/>
#365: nil.setStringValue causes SIGABRT -------------------------------+-------------------------------------------- Reporter: cwdinfo@… | Owner: lsansonetti@… Type: defect | Status: closed Priority: major | Milestone: MacRuby 0.5 Component: MacRuby | Resolution: fixed Keywords: 32-bit, SIGABRT | -------------------------------+-------------------------------------------- Changes (by lsansonetti@…): * status: new => closed * resolution: => fixed * milestone: => MacRuby 0.5 Comment: Should be fixed in r2745. -- Ticket URL: <http://www.macruby.org/trac/ticket/365#comment:2> MacRuby <http://macruby.org/>
participants (1)
-
MacRuby