From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: About cleaning up the thread stuff
Date: Wed, 19 Jan 2005 00:05:20 +0100 [thread overview]
Message-ID: <87zmz6l4nj.fsf@zagadka.de> (raw)
In-Reply-To: <87k6qawg36.fsf@zip.com.au> (Kevin Ryde's message of "Wed, 19 Jan 2005 09:02:53 +1100")
Kevin Ryde <user42@zip.com.au> writes:
> Marius Vollmer <marius.vollmer@uni-dortmund.de> writes:
>>
>> dead-locks might be detected
>
> I wouldn't worry about that. I think the combinations of things a
> thread can block on will make it too hard to be sure a deadlock is
> occurring. There might even be some weird apparent deadlock that's
> meant to be broken by a signal handler cancelling one thread or
> something.
Yes, true. Maybe the debugger could still try to figure out whether
there is a dead-lock, or the program could explicitely ask for it.
Etc.
>> mutexes can be recursive
>
> Yep, I think that's friendliest.
I think there is use for both kinds of mutexes. Sometimes you want a
recursive one, sometimes locking twice from the same thread is an
error.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2005-01-18 23:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 15:54 About cleaning up the thread stuff Marius Vollmer
2005-01-18 17:00 ` Marius Vollmer
2005-01-18 18:03 ` Julian Graham
2005-01-18 21:03 ` Marius Vollmer
2005-01-18 18:08 ` Andy Wingo
2005-01-18 21:04 ` Marius Vollmer
2005-01-18 22:02 ` Kevin Ryde
2005-01-18 23:05 ` Marius Vollmer [this message]
2005-01-19 0:02 ` Kevin Ryde
2005-02-01 16:02 ` Marius Vollmer
2005-03-02 21:09 ` Marius Vollmer
2005-03-04 0:46 ` Kevin Ryde
2005-03-04 11:33 ` 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=87zmz6l4nj.fsf@zagadka.de \
--to=mvo@zagadka.de \
--cc=guile-devel@gnu.org \
/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).