GNU bug report logs - #36649
27.0.50; pure space and pdumper

Previous Next

Full log

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

From: Pip Cet <pipcet <at> gmail.com>
To: Robert Pluim <rpluim <at> gmail.com>
Cc: 36649 <at> debbugs.gnu.org, Paul Eggert <eggert <at> cs.ucla.edu>
Subject: Re: bug#36649: 27.0.50; pure space and pdumper
Date: Sun, 21 Jul 2019 18:07:43 +0000

[Message part 1 (text/plain, inline)]

On Sun, Jul 21, 2019 at 5:56 PM Robert Pluim <rpluim <at> gmail.com> wrote:
> >>>>> On Sun, 21 Jul 2019 17:43:05 +0000, Pip Cet <pipcet <at> gmail.com> said:
>
>     Pip> On Sun, Jul 21, 2019 at 3:06 PM Robert Pluim <rpluim <at> gmail.com> wrote:
>     >> Hmm, it crashed the first time I ran make, then I got distracted, so I
>     >> ran make again later, and this time it built:
>     >>
>     >> make[2]: Nothing to be done for `all'.
>     >> ELC      char-fold.elc
>     >> freeing symbol def-tmp-var
>
>     Pip> Hmm. So it worked with the second patch, but only when you reran make?
>     Pip> That's strange. Looking at the crash backtrace again, it seems that
>     Pip> this is the initial garbage collection, when everything should be
>     Pip> pristine. I still think it dies while marking the obarray, upon
>     Pip> encountering a symbol which has somehow become corrupted...
>
> OK. How do we go about detecting which symbol that is?

I'm not sure about debugging on macOS, but can you get a full
backtrace, or a core dump, or both? We're particularly interested in
what "i" is in mark_vectorlike.

Otherwise, the attached patch should produce (probably a lot of)
information, the last lines of which would be interesting...

[0001-Other-debugging-changes.patch (text/x-patch, attachment)]

Previous Next

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