From: Linas Vepstas <linasvepstas@gmail.com>
To: Andy Wingo <wingo@pobox.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 16:29:38 -0600 [thread overview]
Message-ID: <CAHrUA37kppwktq_U7DO3mYXT6vp9VdsLB83p2XReF7t2XkO5Ag@mail.gmail.com> (raw)
In-Reply-To: <87mvex8f4c.fsf@pobox.com>
Hi Andy: I just code-reviewed, it looks like a good fix; you're saying that
the dynamic state was being accidentally collected when it shouldn't
have been.
Tested, it tests OK, after 40 mins cpu time, its still running.
--linas
next prev parent reply other threads:[~2017-01-11 22:29 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
2017-01-11 22:29 ` Linas Vepstas [this message]
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=CAHrUA37kppwktq_U7DO3mYXT6vp9VdsLB83p2XReF7t2XkO5Ag@mail.gmail.com \
--to=linasvepstas@gmail.com \
--cc=25387-done@debbugs.gnu.org \
--cc=wingo@pobox.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).