[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#66098: Crash in itree.c on macOS with incomplete backtrace
From: |
Stefan Kangas |
Subject: |
bug#66098: Crash in itree.c on macOS with incomplete backtrace |
Date: |
Sat, 23 Sep 2023 04:56:56 -0700 |
Robert Pluim <rpluim@gmail.com> writes:
> 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.
My workflow is that I pull and rebuild many times a day, in the same
repository as I run the Emacs I use daily from. When I start or restart
Emacs, that version is just whatever happens to have been built last.
So I unfortunately don't think git reflog or numbered builds will help
with finding this information in my case.
bug#66098: Crash in itree.c on macOS with incomplete backtrace, Eli Zaretskii, 2023/09/19
- bug#66098: Crash in itree.c on macOS with incomplete backtrace, Stefan Kangas, 2023/09/22
- bug#66098: Crash in itree.c on macOS with incomplete backtrace, Eli Zaretskii, 2023/09/22
- bug#66098: Crash in itree.c on macOS with incomplete backtrace, Robert Pluim, 2023/09/22
- bug#66098: Crash in itree.c on macOS with incomplete backtrace,
Stefan Kangas <=
- bug#66098: Crash in itree.c on macOS with incomplete backtrace, Eli Zaretskii, 2023/09/23
- bug#66098: Crash in itree.c on macOS with incomplete backtrace, Stefan Kangas, 2023/09/24
- bug#66098: Crash in itree.c on macOS with incomplete backtrace, Eli Zaretskii, 2023/09/24
- bug#66098: Crash in itree.c on macOS with incomplete backtrace, Stefan Kangas, 2023/09/24
- bug#66098: Crash in itree.c on macOS with incomplete backtrace, Stefan Kangas, 2023/09/24
- bug#66098: Crash in itree.c on macOS with incomplete backtrace, Gerd Möllmann, 2023/09/24
bug#66098: Crash in itree.c on macOS with incomplete backtrace, Gerd Möllmann, 2023/09/19