GNU bug report logs - #60220
29.0.60; macOS 13.1 crash shortly after starting Emacs

Previous Next

Full log

Message #38 received at 60220 <at> debbugs.gnu.org (full text, mbox):

From: Aaron Jensen <aaronjensen <at> gmail.com>
To: Gerd Möllmann <gerd.moellmann <at> gmail.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 60220 <at> debbugs.gnu.org
Subject: Re: bug#60220: 29.0.60; macOS 13.1 crash shortly after starting Emacs
Date: Thu, 22 Dec 2022 00:12:35 -0500

On Thu, Dec 22, 2022 at 12:09 AM Aaron Jensen <aaronjensen <at> gmail.com> wrote:
>
> On Wed, Dec 21, 2022 at 8:29 AM Gerd Möllmann <gerd.moellmann <at> gmail.com> wrote:
> >
> > If I remember that correctly, installed signal handlers don’t survive process replacement. The man pages for execve and sigaction should tell.
>
> If I'm reading this correctly, that is the case:
>
> Signals set to be ignored in the calling process are set to be ignored
> in the new process. Signals which are set to be caught in the calling
> process image are set to default action in the new process image.
> Blocked
> signals remain blocked regardless of changes to the signal action.
> The signal stack is reset to be undefined (see sigaction(2) for more
> information).
>
>
>
> I have not had a crash today. I have also not restarted Emacs via restart-emacs.


Is this of any relevance?

File descriptors open in the calling process image remain open in the
new process image, except for those for which the close-on-exec flag
is set (see close(2) and fcntl(2)).  Descriptors that remain open are
unaffected by execve().

Aaron

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.