From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: guile threading deadlock
Date: Sat, 08 Nov 2008 13:25:23 +0100 [thread overview]
Message-ID: <87fxm25rrg.fsf@gnu.org> (raw)
In-Reply-To: 3ae3aa420811071826q7e4a153at16a67efbe7261b6d@mail.gmail.com
Hello!
"Linas Vepstas" <linasvepstas@gmail.com> writes:
> I've got a little deadlock problem w/ guile. Here's the pseudocode:
>
> for (i=0; i<10 i++) {
> pthread_create (load_scm, expr[i]);
> }
>
> void load_scm (char * expr) {
> scm_init_guile();
> scm_c_eval(expr);
> /* and pthread exit now that we're done */
> }
>
> The expr's are entirely scm lambda defines of one sort or another,
> and do not do any actual computation.
Can you try to provide actual code to reproduce the problem? :-)
That would be great.
Did you compile Guile with thread support (Debian's package doesn't have
thread support)? If not, that may be the problem. See
http://thread.gmane.org/gmane.lisp.guile.devel/7754 for details.
> #12 0xf7828a43 in on_thread_exit (v=0x9179e18) at threads.c:505
> #13 0xf7e3bbb0 in __nptl_deallocate_tsd ()
> from /lib/tls/i686/cmov/libpthread.so.0
> #14 0xf7e3c509 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
> #15 0xf7c3ae5e in clone () from /lib/tls/i686/cmov/libc.so.6
>
> Not sure who called clone ... not my code ... this is confusing. ...
The C library.
Hope this helps,
Ludo'.
next prev parent reply other threads:[~2008-11-08 12:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 2:26 guile threading deadlock Linas Vepstas
2008-11-08 12:25 ` Ludovic Courtès [this message]
2008-11-08 18:29 ` Linas Vepstas
2008-11-09 17:13 ` Ludovic Courtès
2008-11-09 19:47 ` Linas Vepstas
2008-11-09 21:14 ` Ludovic Courtès
2008-11-09 22:16 ` Linas Vepstas
2008-11-09 23:36 ` Ludovic Courtès
2008-11-10 23:59 ` Linas Vepstas
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=87fxm25rrg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-user@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).