From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Cc: bug-guile@gnu.org
Subject: Re: [bug #33996] 2.0.2: Crash related to ports and threads
Date: Sun, 21 Aug 2011 15:22:52 +0200 [thread overview]
Message-ID: <87r54ex5jn.fsf@gnu.org> (raw)
In-Reply-To: 871uwjhxi2.fsf@pobox.com
Hi!
Andy Wingo <wingo@pobox.com> skribis:
> Oh dear, this is a nasty one. The issue is that Guile's ports are not
> threadsafe. I hadn't thought about this one...
>
> I am adding guile-devel to the Cc for input. Any fix to this will be
> pretty big, I think. I think that the right fix here is probably what
> Glibc does; see `info libc "Streams and Threads"` for the full details.
Indeed, it would probably need per-port mutexes, making I/O primitives
thread-safe by default, and perhaps providing unlocked variants like
libc does.
Putting our fat mutexes on a diet seems like a prerequisite...
Thanks,
Ludo’.
prev parent reply other threads:[~2011-08-21 13:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 7:42 [bug #33996] 2.0.2: Crash related to ports and threads Cedric Cellier
2011-08-18 9:36 ` Andy Wingo
2011-08-21 13:22 ` Ludovic Courtès [this message]
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=87r54ex5jn.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-guile@gnu.org \
--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).