GNU bug report logs - #17168
24.3.50; Segfault at mark_object

Previous Next

Full log

Message #98 received at 17168 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Monnier <monnier <at> IRO.UMontreal.CA>
Cc: 17168 <at> debbugs.gnu.org, dancol <at> dancol.org, dmantipov <at> yandex.ru
Subject: Re: bug#17168: 24.3.50; Segfault at mark_object
Date: Sun, 06 Apr 2014 18:06:56 +0300

> From: Stefan Monnier <monnier <at> IRO.UMontreal.CA>
> Date: Sun, 06 Apr 2014 08:36:02 -0400
> Cc: Dmitry Antipov <dmantipov <at> yandex.ru>, 17168 <at> debbugs.gnu.org
> 
> > This scheme works and passes Dmitry's test, but the resulting
> > Vpure_reachable vector has over 8,000 items. Most of these items are
> > ordinary interned symbols.
> 
> What objects are there besides symbols in Vpure_reachable?
> If we can reduce Vpure_reachable to only contain symbols, then we can
> replace it with a `pinned' bit in the Lisp_Symbol struct and then walk
> the list of symbols during mark, marking all those symbols with the
> `pinned' bit.

As an alternative, would it make sense to try to understand why the
problems started when they did?  IOW, how come we never saw this until
now?

In http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15583#23, Richard
provided the last good revno (113938) and the first bad one (114268);
I looked at that range of revisions, and 114156 looks relevant.  How
about if we revert it and see if the problems go away?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.