From: Kevin Ryde <user42@zip.com.au>
Subject: pthread fast mutexes
Date: Tue, 24 Feb 2004 07:16:50 +1000 [thread overview]
Message-ID: <87ishxv6m5.fsf@zip.com.au> (raw)
In the current cvs on my i386 debian,
(unlock-mutex (make-mutex))
gives a seg fault.
I'm guessing it's because make-mutex uses a pthread fast mutex, and
that style means no error checking by the unlock.
Maybe the scheme level functions will need to use the "normal" mutexes
so the above can throw an exception. Or is there some other theory on
this?
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2004-02-23 21:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 21:16 Kevin Ryde [this message]
2004-02-23 22:05 ` pthread fast mutexes Mikael Djurfeldt
2004-02-23 22:22 ` Mikael Djurfeldt
2004-02-23 23:46 ` Kevin Ryde
2004-02-24 0:02 ` Mikael Djurfeldt
2004-02-28 20:18 ` Kevin Ryde
2004-03-20 22:51 ` Marius Vollmer
2004-02-23 22:33 ` Kevin Ryde
2004-02-24 1:17 ` Mikael Djurfeldt
2004-03-20 22:51 ` Marius Vollmer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ishxv6m5.fsf@zip.com.au \
--to=user42@zip.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).