From: ludo@gnu.org (Ludovic Courtès)
To: Mike Gran <spk121@yahoo.com>
Cc: "13611@debbugs.gnu.org" <13611@debbugs.gnu.org>
Subject: bug#13611: SEGV during SMOB GC
Date: Tue, 05 Feb 2013 22:13:09 +0100 [thread overview]
Message-ID: <87a9rih3bu.fsf@gnu.org> (raw)
In-Reply-To: <1360083888.57707.YahooMailNeo@web120402.mail.ne1.yahoo.com> (Mike Gran's message of "Tue, 5 Feb 2013 09:04:48 -0800 (PST)")
Mike Gran <spk121@yahoo.com> skribis:
>>> Is that expected that GC is sometimes called from a
>
>>> thread where scm_i_current_thread is null and sometimes
>>> called from a thread where scm_i_current_thread is
>>> not null?
>>
>> Can you check whether your GC was built with --enable-parallel-mark?
>>
>> I’m confident that the SMOB mark procedure is never called with null
>> scm_i_current_thread with 7.2 compiled with the default options (the
>> GnuTLS bindings rely on this, and I had not seen any such report until
>> someone tried with GC 7.3pre, which uses the parallel marker by
>> default.)
>
> It looks like fedora gc rpms do use --enable-parallel-mark
> for x86 architectures.
Then that’s the problem.
> But it looks like it has been that way for a long time.
> Since 2005 at least.
And you did not have the problem before? That part of Guile hasn’t
changed in a long time, I think.
Ludo’.
next prev parent reply other threads:[~2013-02-05 21:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-02 20:51 bug#13611: SEGV during SMOB GC Mike Gran
2013-02-05 10:07 ` Ludovic Courtès
2013-02-05 16:29 ` Mike Gran
2013-02-05 16:41 ` Ludovic Courtès
2013-02-05 17:04 ` Mike Gran
2013-02-05 21:13 ` Ludovic Courtès [this message]
2013-02-06 4:56 ` Mike Gran
2013-03-01 17:02 ` Ludovic Courtès
2013-03-13 12:42 ` Andy Wingo
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=87a9rih3bu.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=13611@debbugs.gnu.org \
--cc=spk121@yahoo.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).