From: Eli Zaretskii <eliz@gnu.org>
To: "Kirill A. Korinsky" <kirill@korins.ky>
Cc: 51336@debbugs.gnu.org, larsi@gnus.org, stefankangas@gmail.com,
alan@idiocy.org
Subject: bug#51336: 29.0.50; Application not responding
Date: Thu, 28 Dec 2023 21:47:34 +0200 [thread overview]
Message-ID: <83cyuq6re1.fsf@gnu.org> (raw)
In-Reply-To: <C13E5205-4431-411F-B565-2F86E9AA3A48@korins.ky> (kirill@korins.ky)
> From: "Kirill A. Korinsky" <kirill@korins.ky>
> Date: Thu, 28 Dec 2023 18:55:02 +0100
> Cc: stefankangas@gmail.com,
> 51336@debbugs.gnu.org,
> Lars Magne Ingebrigtsen <larsi@gnus.org>,
> alan@idiocy.org
>
> I've reproduced this issue a few times and attached lldb to see where it blocked.
>
> All attempts were the same:
>
> > (lldb) bt all
> > * thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP
> > * frame #0: 0x00007ff817ed220a libsystem_kernel.dylib`__read_nocancel + 10
> > frame #1: 0x00007ff817de5fb9 libsystem_c.dylib`_sread + 16
> > frame #2: 0x00007ff817de5f68 libsystem_c.dylib`__srefill1 + 24
> > frame #3: 0x00007ff817de39b8 libsystem_c.dylib`__svfscanf_l + 2059
> > frame #4: 0x00007ff817e39a2f libsystem_c.dylib`scanf + 196
> > frame #5: 0x000000010ea0800a emacsql-sqlite`main + 234
> > frame #6: 0x00000001173db52e dyld`start + 462
> > (lldb)
Thanks, but I have no idea what this could mean. What is the source
of the SIGSTOP signal?
next prev parent reply other threads:[~2023-12-28 19:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 17:13 bug#51336: 29.0.50; Application not responding Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-24 18:34 ` Lars Ingebrigtsen
2021-10-24 19:44 ` Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-24 19:45 ` Lars Ingebrigtsen
2021-10-24 20:25 ` Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-25 9:19 ` Alan Third
2022-09-13 14:47 ` Lars Ingebrigtsen
2022-09-13 14:49 ` Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-13 15:02 ` Lars Ingebrigtsen
2022-09-13 17:05 ` Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-03 8:46 ` Stefan Kangas
2023-09-03 8:49 ` Kirill A. Korinsky via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-03 9:03 ` Eli Zaretskii
2023-12-28 17:55 ` Kirill A. Korinsky
2023-12-28 19:47 ` Eli Zaretskii [this message]
2024-01-12 16:31 ` Kirill Korinsky
2024-01-12 17:22 ` Alan Third
2024-01-12 18:14 ` Eli Zaretskii
2024-01-12 18:31 ` Alan Third
2024-01-12 23:53 ` Kirill Korinsky
2024-01-13 6:51 ` Eli Zaretskii
2024-01-13 22:41 ` Kirill Korinsky
2024-01-20 9:23 ` Eli Zaretskii
2024-01-20 13:19 ` Kirill A. Korinsky
2024-01-23 15:33 ` Kirill A. Korinsky
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=83cyuq6re1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51336@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=kirill@korins.ky \
--cc=larsi@gnus.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 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.