From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: adamkshannon@gmail.com, 74369@debbugs.gnu.org
Subject: bug#74369: 29.4; Freeze on Intel Mac
Date: Sat, 16 Nov 2024 14:02:17 +0100 [thread overview]
Message-ID: <m2wmh3pc12.fsf@gmail.com> (raw)
In-Reply-To: <86h687gxrf.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 16 Nov 2024 14:37:40 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Gerd Möllmann <gerd.moellmann@gmail.com>
>> Cc: Adam Shannon <adamkshannon@gmail.com>, 74369@debbugs.gnu.org
>> Date: Sat, 16 Nov 2024 10:42:49 +0100
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> >> From: Adam Shannon <adamkshannon@gmail.com>
>> >> Date: Fri, 15 Nov 2024 10:11:26 -0600
>> >>
>> >> In GNU Emacs 29.4 (build 1, x86_64-apple-darwin18.7.0, NS appkit-1671.60
>> >> Version 10.14.6 (Build 18G9323)) of 2024-08-02 built on
>> >> builder10-14.lan
>> >> Windowing system distributor 'Apple', version 10.3.2487
>> >> System Description: macOS 14.7.1
>> >
>> > Thanks, but without a recipe to reproduce this, or at least a
>> > description of what happened, I don't see how we can investigate this.
>> > Also, please describe in more detail what does "freeze" mean in this
>> > case.
>> >
>> > The call-stack you posted indicates this is a nested debugger call,
>> > because the original error, signaled by Lisp, somehow caused the
>> > debugger to hit another error. But a lot of important details are
>> > missing.
>>
>> FWIW, I think this is bug#72496.
>
> Thanks, feel free to merge them if you think they are the same bug.
Done.
prev parent reply other threads:[~2024-11-16 13:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 16:11 bug#74369: 29.4; Freeze on Intel Mac Adam Shannon
2024-11-15 19:45 ` Ship Mints
2024-11-16 8:50 ` Eli Zaretskii
2024-11-16 9:42 ` Gerd Möllmann
2024-11-16 12:37 ` Eli Zaretskii
2024-11-16 13:02 ` Gerd Möllmann [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2wmh3pc12.fsf@gmail.com \
--to=gerd.moellmann@gmail.com \
--cc=74369@debbugs.gnu.org \
--cc=adamkshannon@gmail.com \
--cc=eliz@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.