From: "Linas Vepstas" <linasvepstas@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-user@gnu.org
Subject: Re: guile threading deadlock
Date: Mon, 10 Nov 2008 17:59:24 -0600 [thread overview]
Message-ID: <3ae3aa420811101559r6c8f1d35x10b05913fb19a4a1@mail.gmail.com> (raw)
In-Reply-To: <874p2ga2ud.fsf@gnu.org>
Hi,
2008/11/9 Ludovic Courtès <ludo@gnu.org>:
> "Linas Vepstas" <linasvepstas@gmail.com> writes:
>
>> However, there is a simple solution: wrap every call
>> to scm_c_eval_string() with a call to scm_with_guile().
>> Doesn't seem very optimal or pretty, but it works.
>
> Cool.
Well, not quite. I also discovered that I have to re-define
smob-based functions in every new thread. That is,
I have to call scm_c_define_gsubr() in each thread
that I plan to use; simply calling these once in some
parent thread results in
ERROR: Unbound variable: whatever-xxx
ABORT: unbound-variable
in the other threads. I find this behaviour "surprising";
is there another spot of documentation that I should have
seen, that explained this, or is this a bug, or is this
working as designed?
> Again, it *is* documented, but maybe not sufficiently prominently, or
> maybe it could be repeated in other places of the manual. Can you say
> specifically how you'd like to change that?
Haven't I answered this question three times now?
I feel that this conversation is not moving forward, I am
not sure why, or what i can do to be more helpful.
> Please send patches to <bug-guile@gnu.org>.
I'll try to do so in the next few says.
> If they are non-trivial,
> you'll need to assign copyright to the FSF, but we can work this out
> off-line in due time.
I have a generic assignment form with the FSF.
--linas
prev parent reply other threads:[~2008-11-10 23:59 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
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 [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=3ae3aa420811101559r6c8f1d35x10b05913fb19a4a1@mail.gmail.com \
--to=linasvepstas@gmail.com \
--cc=guile-user@gnu.org \
--cc=ludo@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).