unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Panicz Maciej Godek <godek.maciek@gmail.com>
To: Chris Vine <chris@cvine.freeserve.co.uk>
Cc: "guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: libguile thread safety
Date: Sat, 4 Jan 2014 02:22:11 +0100	[thread overview]
Message-ID: <CAMFYt2Z9qa0C2Rjay73KtEb56d5dSeNWYo=GSxuMbUSEBYjzYA@mail.gmail.com> (raw)
In-Reply-To: <CAMFYt2bNkr8_zPtcT4uGQtkvrAuW9nJVbuRpv3jt9xzAmGS4BQ@mail.gmail.com>

I concluded that this might be a solution. I tested it with 2.0.5 from
ubuntu repository. I had to add GC_allow_register_threads (and link
against gc, accordingly), because otherwise the program aborted with
the message "Threads explicit registering is not previously enabled"
whenever it attempted to create a thread.

For some reason the initialization routine needs to call
scm_c_eval_string; otherwise it doesn't help.

The solution doesn't fill me with joy, but I hope it works for you

#include <libguile.h>
#include <pthread.h>

void *guile_wrapper (void *data) {
  scm_c_eval_string ("(display \"Hello\n\")");
  return NULL;
}

void *thread_func (void *data) {
  scm_with_guile (&guile_wrapper, NULL);
  return NULL;
}

void *do_nothing(void *unused) {
  scm_c_eval_string("(noop)");
  return NULL;
}

int main () {
  pthread_t thread1;
  pthread_t thread2;

  GC_allow_register_threads();

  scm_with_guile(do_nothing, NULL);

  pthread_create (&thread1, NULL, thread_func, NULL);
  pthread_create (&thread2, NULL, thread_func, NULL);

  pthread_join (thread1, NULL);
  pthread_join (thread2, NULL);

  return 0;
}



  reply	other threads:[~2014-01-04  1:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03 23:34 libguile thread safety Chris Vine
2014-01-04  0:00 ` Ludovic Courtès
2014-01-04 17:19   ` Chris Vine
2014-01-04  0:08 ` Panicz Maciej Godek
2014-01-04  0:22   ` Chris Vine
2014-01-04  0:56     ` Panicz Maciej Godek
2014-01-04  1:22       ` Panicz Maciej Godek [this message]
2014-01-04  9:39         ` Chris Vine
2014-01-04 21:28           ` Mark H Weaver
2014-01-04  1:59 ` Mark H Weaver
2014-01-04  9:50   ` Chris Vine
2014-01-04 12:44   ` Chris Vine
2014-01-04 15:01     ` Panicz Maciej Godek
2014-01-04 17:16       ` Chris Vine
2014-01-04 19:37       ` Mark H Weaver
2014-01-04 21:01         ` Chris Vine
2014-01-04 22:43           ` Panicz Maciej Godek
2014-01-04 23:31             ` Chris Vine
2014-01-05 13:15               ` Panicz Maciej Godek
2014-01-05 17:37                 ` Mark H Weaver
2014-03-18 10:49                   ` Chris Vine
2014-03-18 15:22                     ` Mark H Weaver
2014-03-18 19:32                       ` Chris Vine

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='CAMFYt2Z9qa0C2Rjay73KtEb56d5dSeNWYo=GSxuMbUSEBYjzYA@mail.gmail.com' \
    --to=godek.maciek@gmail.com \
    --cc=chris@cvine.freeserve.co.uk \
    --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).