From: Andy Wingo <wingo@pobox.com>
To: Linas Vepstas <linasvepstas@gmail.com>
Cc: 25387-done@debbugs.gnu.org
Subject: bug#25387: guile-2.2 multi-thread segfault in SCM_VALIDATE_WEAK_TABLE
Date: Wed, 11 Jan 2017 22:24:03 +0100 [thread overview]
Message-ID: <87mvex8f4c.fsf@pobox.com> (raw)
In-Reply-To: <87tw97999p.fsf@pobox.com> (Andy Wingo's message of "Mon, 09 Jan 2017 23:08:18 +0100")
On Mon 09 Jan 2017 23:08, Andy Wingo <wingo@pobox.com> writes:
> On Sun 08 Jan 2017 01:18, Linas Vepstas <linasvepstas@gmail.com> writes:
>
>> Following program crashes immediately (fraction of a second)
>> in guile-2.2, current git version (as of 29 Dec 2016
>> a0656ad4cf976b3845e9b9663a90b46b4cf9fc5a )
>
> Nice bug, thank you! I will have a look.
Fixed in master, I think. Have a look!
commit 63bf6ffa0d3cdddf8151cc80ac18fe5dfb614587
Author: Andy Wingo <wingo@pobox.com>
Date: Wed Jan 11 22:17:24 2017 +0100
Protect call-with-new-thread data from GC.
* libguile/threads.c (struct launch_data): Add prev/next pointers.
(protected_launch_data, protected_launch_data_lock): New static vars.
(protect_launch_data, unprotect_launch_data): New functions.
(really_launch, scm_sys_call_with_new_thread): Preserve launch data
from GC. Thanks to Linas Vepstas for the report!
Cheers,
Andy
next prev parent reply other threads:[~2017-01-11 21:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-08 0:18 bug#25387: guile-2.2 multi-thread segfault in SCM_VALIDATE_WEAK_TABLE Linas Vepstas
2017-01-08 0:21 ` bug#25387: also crashes in guile-2.0 Linas Vepstas
2017-01-09 22:08 ` bug#25387: guile-2.2 multi-thread segfault in SCM_VALIDATE_WEAK_TABLE Andy Wingo
2017-01-11 21:24 ` Andy Wingo [this message]
2017-01-11 22:29 ` Linas Vepstas
2017-01-10 17:37 ` bug#25387: better but still an issue 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=87mvex8f4c.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=25387-done@debbugs.gnu.org \
--cc=linasvepstas@gmail.com \
/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).