GNU bug report logs - #77408
[PATCH] srfi-18: Unlock mutex even when condition variable timeout is hit

Previous Next

Package: guile;

Reported by: nathan <nathan_mail <at> nborghese.com>

Date: Mon, 31 Mar 2025 16:04:04 UTC

Severity: normal

Tags: patch

To reply to this bug, email your comments to 77408 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to bug-guile <at> gnu.org:
bug#77408; Package guile. (Mon, 31 Mar 2025 16:04:05 GMT) Full text and rfc822 format available.
Acknowledgement sent to nathan <nathan_mail <at> nborghese.com>:
New bug report received and forwarded. Copy sent to bug-guile <at> gnu.org. (Mon, 31 Mar 2025 16:04:05 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: nathan <nathan_mail <at> nborghese.com>
To: bug-guile <at> gnu.org
Subject: [PATCH] srfi-18: Unlock mutex even when condition variable timeout is
 hit
Date: Mon, 31 Mar 2025 16:02:52 +0000

[Message part 1 (text/plain, inline)]
Unlock mutex even when condition variable timeout is hit
Add tests

Relevant srfi-18 documentation:
https://srfi.schemers.org/srfi-18/srfi-18.html
NOTE: mutex-unlock! is related to the "wait" operation on condition variables available in other thread systems. The main difference is that "wait" automatically locks mutex just after the thread is unblocked. This operation is not performed by mutex-unlock! and so must be done by an explicit call to mutex-lock!.
[0001-srfi-18-Unlock-mutex-even-when-condition-variable-ti.patch (text/x-patch, attachment)]
This bug report was last modified 4 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.