Projects

Ticket #493 (closed defect: fixed)

Opened 2 years ago

Last modified 14 months ago

signals cannot be intercepted

Reported by: lsansonetti@… Owned by: martinlagardette@…
Priority: blocker Milestone: MacRuby 0.8
Component: MacRuby Keywords:
Cc: ernest.prabhakar@…

Description

Currently MacRuby doesn't allow you to catch signals (via the Kernel#trap method). This should be implemented in the final 0.5 release.

Change History

Changed 2 years ago by ernest.prabhakar@…

  • cc ernest.prabhakar@… added

Cc Me!

Changed 2 years ago by martinlagardette@…

  • status changed from new to assigned

Changed 2 years ago by martinlagardette@…

Signals are now partially implemented in r3338, with some limitations: - Raising an exception within a signal handler will not work - Ruby doesn't handle any signal by default, except SIGBUS, SIGSEGV, SIGPIPE, and SIGCHLD

Changed 2 years ago by ernest.prabhakar@…

Great, mspec/bin/mspec -B spec/macruby.mspec spec/macruby/core/gcd/source_spec.rb now seems to run properly. (versus failing randomly every few runs).

Please check against it if you make further changes. :-)

Changed 14 months ago by lsansonetti@…

  • status changed from assigned to closed
  • resolution set to fixed
  • milestone changed from MacRuby 0.5 to MacRuby 0.8

I think this bug can be closed, as signals can now be intercepted. I also believe we have an open bug regarding exceptions raised inside signal handlers.

Note: See TracTickets for help on using tickets.