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 17:41:22 +0100 [thread overview]
Message-ID: <876226sogd.fsf@gnu.org> (raw)
In-Reply-To: <1360081788.3781.YahooMailNeo@web120406.mail.ne1.yahoo.com> (Mike Gran's message of "Tue, 5 Feb 2013 08:29:48 -0800 (PST)")
Hi,
Mike Gran <spk121@yahoo.com> skribis:
>> From: Ludovic Courtès <ludo@gnu.org>
>
>> Is there any chance that you’re using a GC 7.3 pre-release?
>
> Using gc-7.2b-2.fc17.i686
OK.
>> There was a similar report on IRC, and the fix appears to be:
>
> It does fix my SEGV
Good.
[...]
> Count of GC SMOB marks from null thread: 176
> Count of GC SMOB marks from current thread: 825
>
> 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.)
Thanks!
Ludo’.
next prev parent reply other threads:[~2013-02-05 16:41 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 [this message]
2013-02-05 17:04 ` Mike Gran
2013-02-05 21:13 ` Ludovic Courtès
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=876226sogd.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).