From: Andy Wingo <wingo@pobox.com>
To: hanwen@xs4all.nl
Cc: guile-devel@gnu.org
Subject: Re: GC asserts and threads
Date: Tue, 09 Sep 2008 09:00:01 +0200 [thread overview]
Message-ID: <m31vzt953i.fsf@pobox.com> (raw)
In-Reply-To: <ga53dn$2c7$1@ger.gmane.org> (Han-Wen Nienhuys's message of "Tue, 09 Sep 2008 02:58:59 -0300")
On Tue 09 Sep 2008 07:58, Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
> Is there any code in GUILE that would create a thread (possibly
> leading to race conditions) when there is no explicit start-thread
> call in the code? The program (lilypond) does run through the
> regular GUILE boot procedure.
Yep, when compiled with threads, guile spawns a separate thread to
handle signals.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2008-09-09 7:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 5:58 GC asserts and threads Han-Wen Nienhuys
2008-09-09 7:00 ` Andy Wingo [this message]
2008-09-09 13:58 ` Han-Wen Nienhuys
2008-09-09 14:53 ` Neil Jerram
2008-09-09 14:06 ` Han-Wen Nienhuys
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=m31vzt953i.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=hanwen@xs4all.nl \
/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).