From: ludo@gnu.org (Ludovic Courtès)
To: Dale Mellor <dale@rdmp.org>
Cc: 15411-done@debbugs.gnu.org
Subject: bug#15411: libguile initialization inside a pthread segfaults
Date: Sun, 13 Oct 2013 16:06:45 +0200 [thread overview]
Message-ID: <87eh7p8du2.fsf@gnu.org> (raw)
In-Reply-To: <1379532999.4818.5.camel@l2> (Dale Mellor's message of "Wed, 18 Sep 2013 20:36:39 +0100")
Hi Dale,
Dale Mellor <dale@rdmp.org> skribis:
> =PROGRAM==============================================================
> #include <libguile.h>
>
>
>
> static void *do_guile (void *)
> {
> for (;;) ;
>
> return nullptr;
> }
>
>
>
> static void *run_thread (void *)
> {
> return scm_with_guile (&do_guile, nullptr);
> }
>
>
>
> int main (int, char **)
> {
> pthread_t thread;
> pthread_create (&thread, nullptr, run_thread, nullptr);
>
> pthread_join (thread, nullptr);
>
> return 0;
> }
>
> =/PROGRAM=============================================================
This program is similar to this test:
http://git.savannah.gnu.org/cgit/guile.git/tree/test-suite/standalone/test-pthread-create-secondary.c
> =SESSION==============================================================
> $ cat /etc/debian_version
> 7.1
>
> $ g++-4.6 --version
> g++-4.6 (Debian 4.6.3-14) 4.6.3
>
> $ guile --version
> guile (GNU Guile) 2.0.5-deb+1-3
The test above appeared in 2.0.6. As the comment notes, this bug was
fixed in libgc after version 7.2alpha5.
Thus, I would recommend upgrading libgc.
I’m closing the bug, but feel free to reopen if you think I got it wrong!
HTH,
Ludo’.
prev parent reply other threads:[~2013-10-13 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 19:36 bug#15411: libguile initialization inside a pthread segfaults Dale Mellor
2013-10-13 14:06 ` Ludovic Courtès [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=87eh7p8du2.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=15411-done@debbugs.gnu.org \
--cc=dale@rdmp.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).