GNU bug report logs - #66098
Crash in itree.c on macOS with incomplete backtrace

Previous Next

Full log

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

From: Robert Pluim <rpluim <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 66098 <at> debbugs.gnu.org, Stefan Kangas <stefankangas <at> gmail.com>
Subject: Re: bug#66098: Crash in itree.c on macOS with incomplete backtrace
Date: Fri, 22 Sep 2023 14:46:31 +0200

>>>>> On Fri, 22 Sep 2023 15:36:22 +0300, Eli Zaretskii <eliz <at> gnu.org> said:

    >> From: Stefan Kangas <stefankangas <at> gmail.com>
    >> Date: Fri, 22 Sep 2023 03:51:33 -0700
    >> Cc: 66098 <at> debbugs.gnu.org
    >> 
    >> Eli Zaretskii <eliz <at> gnu.org> writes:
    >> 
    >> >> From: Stefan Kangas <stefankangas <at> gmail.com>
    >> >> Date: Tue, 19 Sep 2023 01:47:41 -0700
    >> >>
    >> >> After rebuilding from master yesterday, I've started seeing frequent
    >> >> crashes (several times a day) on macOS.
    >> >
    >> > When was your previous build done, and with what HEAD commit?
    >> 
    >> I think I lost that information when I rebuilt, unless we save it
    >> automatically somewhere.

    Eli> Does "git reflog" help?

This is why we have the numbered emacs builds in 'src/', no? Of
course that wonʼt help if you clean before building.

Robert
-- 

Previous Next

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