Summary

mutex-lock! leaves mutex in wrong state

Metadata

• Id: 771225edd2b192eaf814c6bb6e0e7a445f28fd6f
• Trac id: 1231
• Type: defect
• Reporter: joergw
• Owner:
• Cc:
• Status: closed
• Component: core libraries
• Estimated difficulty:
• Resolution: fixed
• Priority: major
• Milestone: 4.11.0
• Version: 4.10.x
• Changetime: 2016-02-14 15:13:52 UTC
• Created: 2015-12-12 13:57:19 UTC
• Keywords: srfi-18

Attachments

• 771225edd2b192eaf814c6bb6e0e7a445f28fd6f/attachments/mutexlock.patch

Description

If (and only if) a thread calling (mutex-lock! <muxtex> #f #f) had to wait for it the mutex state is left to be owned by the calling thread instead of 'not-owned.

Changes and comments

[2015-12-12 13:59:45 UTC] joergw attached mutexlock.patch (description=Patch including test.)

[2016-01-23 12:17:49 UTC] sjamaan changed milestone from someday to 4.11.0

[2016-02-14 15:13:52 UTC] sjamaan changed status from new to closed

[2016-02-14 15:13:52 UTC] sjamaan set resolution to fixed

[2016-02-14 15:13:52 UTC] sjamaan wrote:

Fixed in master by 7fcb9fe, in srfi-18 egg by r33191.