Summary

CHICKEN_interrupt() may not work in certain situations

Metadata

• Id: e4b01525e6054fe0661957f5e408fdb3bba346d3
• Trac id: 110
• Type: defect
• Reporter: felix
• Owner:
• Cc:
• Status: closed
• Component: core libraries
• Estimated difficulty:
• Resolution: worksforme
• Priority: minor
• Milestone:
• Version: 4.2.x
• Changetime: 2014-05-03 18:15:36 UTC
• Created: 2009-11-08 02:25:09 UTC
• Keywords:

Description

If the scheduler is currently running, then `CHICKEN_interrupt()` is ineffective. This is unfortunate, since it provides an easy way to let native threads signal events to Scheme.

Changes and comments

[2010-07-20 01:57:14 UTC] felix changed status from new to assigned

[2010-07-20 01:57:14 UTC] felix removed owner felix

[2014-05-03 18:15:36 UTC] sjamaan changed status from assigned to closed

[2014-05-03 18:15:36 UTC] sjamaan set resolution to worksforme

[2014-05-03 18:15:36 UTC] sjamaan wrote:

Felix and I just looked through this and it seems to be working just fine. The interrupt handling has been overhauled during the 4.8.0 development cycle, so it might've been fixed by this overhaul without us being aware of it.