From: Ken Raeburn <raeburn@raeburn.org>
Cc: guile-devel@gnu.org
Subject: Re: segfault in 1.7.91
Date: Sat, 18 Feb 2006 11:51:48 -0500 [thread overview]
Message-ID: <D02B1731-0CE0-49C9-B814-DF9B2F4D72F3@raeburn.org> (raw)
In-Reply-To: <20060217111824.GA13802@basalt.office.altlinux.org>
On Feb 17, 2006, at 06:18, Stanislav Ievlev wrote:
> Greetings!
>
> It is unable to call callback from thread in guile extension.
Does it work if you use scm_with_guile in that thread, as described
in the documentation?
(from doc/ref/api-init.texi)
Each thread that wants to use functions from the Guile API needs to
put itself into guile mode with either @code{scm_with_guile} or
@code{scm_init_guile}. The global state of Guile is initialized
automatically when the first thread enters guile mode.
Ken
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-02-18 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 11:18 segfault in 1.7.91 Stanislav Ievlev
2006-02-18 16:51 ` Ken Raeburn [this message]
2006-02-20 9:00 ` Stanislav Ievlev
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=D02B1731-0CE0-49C9-B814-DF9B2F4D72F3@raeburn.org \
--to=raeburn@raeburn.org \
--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).