From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 66098@debbugs.gnu.org, Stefan Kangas <stefankangas@gmail.com>
Subject: bug#66098: Crash in itree.c on macOS with incomplete backtrace
Date: Fri, 22 Sep 2023 14:46:31 +0200 [thread overview]
Message-ID: <87wmwis7dk.fsf@gmail.com> (raw)
In-Reply-To: <83bkdu75bt.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 22 Sep 2023 15:36:22 +0300")
>>>>> On Fri, 22 Sep 2023 15:36:22 +0300, Eli Zaretskii <eliz@gnu.org> said:
>> From: Stefan Kangas <stefankangas@gmail.com>
>> Date: Fri, 22 Sep 2023 03:51:33 -0700
>> Cc: 66098@debbugs.gnu.org
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> >> From: Stefan Kangas <stefankangas@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
--
next prev parent reply other threads:[~2023-09-22 12:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 8:47 bug#66098: Crash in itree.c on macOS with incomplete backtrace Stefan Kangas
2023-09-19 9:23 ` Robert Pluim
2023-09-19 10:09 ` Robert Pluim
2023-09-20 8:08 ` Paul Eggert
2023-09-20 8:22 ` Robert Pluim
2023-09-22 10:58 ` Stefan Kangas
2023-09-22 12:07 ` Robert Pluim
2023-09-23 13:02 ` Stefan Kangas
2023-09-25 8:36 ` Robert Pluim
2023-09-19 11:24 ` Eli Zaretskii
2023-09-22 10:51 ` Stefan Kangas
2023-09-22 12:36 ` Eli Zaretskii
2023-09-22 12:46 ` Robert Pluim [this message]
2023-09-23 11:56 ` Stefan Kangas
2023-09-23 12:42 ` Eli Zaretskii
2023-09-24 10:55 ` Stefan Kangas
2023-09-24 12:10 ` Eli Zaretskii
2023-09-24 12:25 ` Stefan Kangas
2023-09-24 21:01 ` Stefan Kangas
2023-09-25 3:38 ` Gerd Möllmann
2023-09-19 11:42 ` Gerd Möllmann
2023-09-19 12:21 ` Gerd Möllmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wmwis7dk.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=66098@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stefankangas@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).