unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Linas Vepstas" <linasvepstas@gmail.com>
To: guile-devel <guile-devel@gnu.org>
Subject: Using define in multiple threads?
Date: Sun, 16 Nov 2008 16:27:20 -0600	[thread overview]
Message-ID: <3ae3aa420811161427t6b2c65d1q4adcd6e9a5689ddc@mail.gmail.com> (raw)

Is it "safe" or "legal" to use define in multiple threads?

I am currently looking at an infinite loop in guile, it looks
like there's a pair with cdr pointing to itself.  The pair is
a hashtable bucket. I'm reading through hashtab.c
and see no locking at all, and so it seems probable that
this circular bucket list was created in a race between
two threads inserting into the same hash table.

Now, the test case which triggers this does nothing
other than defines --  it loads a set of files, one per thread,
and, for good measure, I reloaded these over and over.
So typically, one will have the same function being
redefined over and over, typically in different threads.
The same function might be getting defined "simultaneously"
in different threads, even.

So-- I was assuming that this would be an inherently
"safe" operation ... but maybe its not? Is there some funky
semantics to define in a multi-threaded environment?

--linas




             reply	other threads:[~2008-11-16 22:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-16 22:27 Linas Vepstas [this message]
2008-11-17 13:18 ` Using define in multiple threads? Han-Wen Nienhuys
2008-11-17 14:57   ` Ludovic Courtès
2008-11-17 20:45     ` Andy Wingo
2008-11-18 10:20       ` Ludovic Courtès
2008-11-19 23:36         ` Neil Jerram
2008-11-19 23:45           ` Andy Wingo
2008-11-20  8:33             ` Ludovic Courtès

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=3ae3aa420811161427t6b2c65d1q4adcd6e9a5689ddc@mail.gmail.com \
    --to=linasvepstas@gmail.com \
    --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).