[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#36649: 27.0.50; pure space and pdumper

From: Pip Cet
Subject: bug#36649: 27.0.50; pure space and pdumper
Date: Sun, 21 Jul 2019 18:07:43 +0000

On Sun, Jul 21, 2019 at 5:56 PM Robert Pluim <address@hidden> wrote:
> >>>>> On Sun, 21 Jul 2019 17:43:05 +0000, Pip Cet <address@hidden> said:
>     Pip> On Sun, Jul 21, 2019 at 3:06 PM Robert Pluim <address@hidden> 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...

Attachment: 0001-Other-debugging-changes.patch
Description: Text Data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]