From: Alexander Adolf <alexander.adolf@condition-alpha.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: 29.0.50 master freeze on macOS
Date: Fri, 15 Jul 2022 18:31:43 +0200 [thread overview]
Message-ID: <e66ecca64a57da2e159a3b3117000596@condition-alpha.com> (raw)
In-Reply-To: <a6db40e2325e28e625eddc9313708a8c@condition-alpha.com>
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
Alexander Adolf <alexander.adolf@condition-alpha.com> writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>> [...]
>> Did you try to attach a debugger?
>
> <face-palm/> Ah, stupid me! Will do next time and post findings here.
It just happened again. This time I attached a debugger, and gave it a
couple of halt/continue cycles to see what's going on.
It turns out that thread #1 appears to get stuck in try_window(),
coincidentally (or maybe not) in exactly the loop updated by commit
ed4ba79ea8f2be2d01f6447910e2c8319908d0d6 earlier today by yourself. See
attached screenshot.
As you can see in the screenshot, some symbol information appears to be
available.
Do you want me to try to dig further into details, or should I pull &
rebuild to include your commit, and see it that fixes it?
Many thanks and looking forward to your thoughts,
--alexander
[-- Attachment #2: Screenshot 2022-07-15 at 18.10.07.png --]
[-- Type: image/png, Size: 1433769 bytes --]
next prev parent reply other threads:[~2022-07-15 16:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 14:05 29.0.50 master freeze on macOS Alexander Adolf
2022-07-14 14:19 ` Eli Zaretskii
2022-07-14 16:02 ` Alexander Adolf
2022-07-15 16:31 ` Alexander Adolf [this message]
2022-07-15 18:04 ` Eli Zaretskii
2022-07-19 15:27 ` Alexander Adolf
2022-07-19 15:35 ` Alexander Adolf
2022-07-19 16:02 ` Eli Zaretskii
2022-07-25 13:26 ` Alexander Adolf
2022-07-25 13:50 ` Eli Zaretskii
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=e66ecca64a57da2e159a3b3117000596@condition-alpha.com \
--to=alexander.adolf@condition-alpha.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.