Summary

check that foreign callback returns take place in the correct order

Metadata

• Id: 00de48b3ae366b57fdaabdff96080a371bce7ed4
• Trac id: 308
• Type: task
• Reporter: felix
• Owner: felix
• Cc:
• Status: closed
• Component: core libraries
• Estimated difficulty:
• Resolution: fixed
• Priority: minor
• Milestone:
• Version: 4.5.x
• Changetime: 2011-04-04 08:31:00 UTC
• Created: 2010-08-08 20:52:10 UTC
• Keywords: foreign callback

Description

Multiple threads or use of continuations may result in returns from foreign callbacks happen not in the required order. By keeping a stack of addresses (for example from a local variable in the callback entry) this could be checked by the runtime system.

Changes and comments

[2010-08-13 12:26:44 UTC] felix changed status from new to closed

[2010-08-13 12:26:44 UTC] felix set resolution to fixed

[2010-08-13 12:26:44 UTC] felix wrote:

Currently only a check for returning twice from the same callback has been implemented by setting a flag inside the callback return-continuation closure, which should handle the case of code doing funny things with continuations.

[2011-04-04 08:31:00 UTC] felix removed milestone 4.6.0

[2011-04-04 08:31:00 UTC] felix wrote:

Milestone 4.6.0 deleted