Opened 2 years ago

Closed 22 months ago

#1231 closed defect (fixed)

mutex-lock! leaves mutex in wrong state

Reported by: joergw Owned by:
Priority: major Milestone: 4.11.0
Component: core libraries Version: 4.10.x
Keywords: srfi-18 Cc:
Estimated difficulty:

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.

Attachments (1)

mutexlock.patch (6.4 KB) - added by joergw 2 years ago.
Patch including test.

Download all attachments as: .zip

Change History (3)

Changed 2 years ago by joergw

Patch including test.

comment:1 Changed 22 months ago by sjamaan

  • Milestone changed from someday to 4.11.0

comment:2 Changed 22 months ago by sjamaan

  • Resolution set to fixed
  • Status changed from new to closed

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

Note: See TracTickets for help on using tickets.