From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: Code review for thread safeness
Date: Tue, 08 Mar 2005 09:36:09 +1100 [thread overview]
Message-ID: <87fyz75bja.fsf@zip.com.au> (raw)
In-Reply-To: <87wtsjw1ro.fsf@zagadka.de> (Marius Vollmer's message of "Mon, 07 Mar 2005 23:04:59 +0100")
Marius Vollmer <mvo@zagadka.de> writes:
>
> If there might be non-local exits, scm_frame_critical_section can be
> used instead.
If an error occurs and a lazy-catch executes, is the mutex unlocked
for that handler?
> Also, there are probably many more places that need to become critical
> sections. We need to find them and use SCM_CRITICAL_SECTION_START/END
> or scm_frame_critical_section, as appropriate.
The ones I've spotted are (I might have posted this before),
gethostbyname
getpwuid
setpwent (etc)
getgrgid
setgrent (etc)
setlocale
scm_mem2symbol
or scm_i_mem2symbol or whatever it is now. I probably won't get a
chance to actually do anything about these.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-03-07 22:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 22:04 Code review for thread safeness Marius Vollmer
2005-03-07 22:36 ` Kevin Ryde [this message]
2005-03-08 1:18 ` Marius Vollmer
2005-03-08 3:18 ` Ken Raeburn
2005-03-09 14:48 ` Marius Vollmer
2005-03-09 16:23 ` Andreas Rottmann
2005-06-18 5:03 ` Ken Raeburn
2005-12-06 18:58 ` 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=87fyz75bja.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).