From: Aaron Jensen <aaronjensen@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: gerd.moellmann@gmail.com, Eli Zaretskii <eliz@gnu.org>,
60220@debbugs.gnu.org
Subject: bug#60220: 29.0.60; macOS 13.1 crash shortly after starting Emacs
Date: Thu, 29 Dec 2022 19:03:47 -0500 [thread overview]
Message-ID: <CAHyO48y_2bgyZRMHbOPi_s+mgi6eEGe7PW1q02N8fYSoUueWEA@mail.gmail.com> (raw)
In-Reply-To: <CAHyO48yjqwsVLBFBRYqnr+S19beh+-B0gYN737tw1kbwF=h7zw@mail.gmail.com>
On Thu, Dec 29, 2022 at 6:59 PM Aaron Jensen <aaronjensen@gmail.com> wrote:
>
> On Thu, Dec 29, 2022 at 6:49 PM Paul Eggert <eggert@cs.ucla.edu> wrote:
> >
> > On 12/29/22 15:46, Aaron Jensen wrote:
> > > have something that eagerly
> > > loads packages on an idle timer (it caches what was loaded when Emacs
> > > is quit).
> >
> > Could it by that the dynamic linker is being invoked recursively? That
> > is, while something is being dynamically linked, a SIGALRM or equivalent
> > arrives, some idle timer code is run, and the dynamic linker is invoked
> > before the outer linker finishes? I imagine that might put some dynamic
> > linkers into a tizzy.
>
>
> I have no idea, would we see that in the trace at all? Here are two
> more crashes: https://gist.github.com/aaronjensen/f7c46857ea93c858f46a639d8880f290
>
> I have been able to reproduce it just now pretty easily, but I still
> can't reproduce it with the debugger attached.
Would it make sense to use block_atimers while loading native lisp? If
that's a workable thing and you can send me a patch I can try it out.
Thanks,
Aaron
next prev parent reply other threads:[~2022-12-30 0:03 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 15:11 bug#60220: 29.0.60; macOS 13.1 crash shortly after starting Emacs Aaron Jensen
2022-12-20 15:25 ` Aaron Jensen
2022-12-20 15:41 ` Eli Zaretskii
2022-12-20 15:59 ` Aaron Jensen
2022-12-20 17:23 ` Eli Zaretskii
2022-12-21 3:47 ` Aaron Jensen
2022-12-21 12:22 ` Eli Zaretskii
2022-12-21 13:29 ` Gerd Möllmann
2022-12-22 5:09 ` Aaron Jensen
2022-12-22 5:12 ` Aaron Jensen
2022-12-22 5:36 ` Gerd Möllmann
2022-12-22 8:18 ` Eli Zaretskii
2022-12-23 2:05 ` Paul Eggert
2022-12-23 2:22 ` Aaron Jensen
2022-12-23 5:33 ` Gerd Möllmann
2022-12-23 5:56 ` Paul Eggert
2022-12-24 6:45 ` Aaron Jensen
2022-12-24 6:57 ` Eli Zaretskii
2022-12-24 7:03 ` Aaron Jensen
2022-12-24 8:25 ` Paul Eggert
2022-12-24 15:11 ` Aaron Jensen
2022-12-25 5:30 ` Gerd Möllmann
2022-12-25 19:30 ` Aaron Jensen
2022-12-25 19:59 ` Eli Zaretskii
2022-12-27 11:12 ` Aaron Jensen
2022-12-27 13:11 ` Eli Zaretskii
2022-12-29 22:47 ` Aaron Jensen
2022-12-29 23:46 ` Aaron Jensen
2022-12-29 23:49 ` Paul Eggert
2022-12-29 23:59 ` Aaron Jensen
2022-12-30 0:03 ` Aaron Jensen [this message]
2022-12-30 1:16 ` Paul Eggert
2022-12-30 1:20 ` Aaron Jensen
2022-12-30 2:11 ` Aaron Jensen
2022-12-30 3:54 ` Aaron Jensen
2022-12-30 4:24 ` Aaron Jensen
2022-12-30 4:25 ` Aaron Jensen
2022-12-30 7:41 ` Gerd Möllmann
2022-12-30 8:03 ` Aaron Jensen
2022-12-30 8:42 ` Gerd Möllmann
2022-12-30 13:37 ` Aaron Jensen
2022-12-30 13:52 ` Aaron Jensen
2022-12-30 14:24 ` Aaron Jensen
2022-12-30 15:27 ` Gerd Möllmann
2022-12-30 15:50 ` Aaron Jensen
2022-12-30 8:37 ` Eli Zaretskii
2022-12-30 13:36 ` Aaron Jensen
2022-12-30 14:18 ` Eli Zaretskii
2022-12-30 22:42 ` Paul Eggert
2022-12-31 6:33 ` Eli Zaretskii
2022-12-30 8:32 ` Eli Zaretskii
2023-01-04 15:51 ` Andrea Corallo
2023-01-04 16:58 ` Eli Zaretskii
2023-01-10 15:28 ` Andrea Corallo
2023-01-10 16:57 ` Eli Zaretskii
2023-01-10 22:59 ` Aaron Jensen
2023-01-12 11:01 ` Andrea Corallo
2023-01-14 16:23 ` Aaron Jensen
2022-12-30 0:08 ` Paul Eggert
2022-12-30 8:29 ` Eli Zaretskii
2022-12-22 8:05 ` Eli Zaretskii
2022-12-20 15:32 ` Eli Zaretskii
2022-12-20 15:36 ` Aaron Jensen
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=CAHyO48y_2bgyZRMHbOPi_s+mgi6eEGe7PW1q02N8fYSoUueWEA@mail.gmail.com \
--to=aaronjensen@gmail.com \
--cc=60220@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=gerd.moellmann@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.