[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#32338: 26.1; term.el broken on macOS
From: |
Constantine Vetoshev |
Subject: |
bug#32338: 26.1; term.el broken on macOS |
Date: |
Sat, 22 Sep 2018 11:12:15 -0700 |
On Thu, Sep 20, 2018 at 5:35 PM Noam Postavsky <npostavs@gmail.com> wrote:
> Okay, I'm going to guess it's the change to use vfork. Here's a patch
> which should undo that change (I can't test it on macOS, and it's just
> assembled from git log --grep=vfork, so I may have missed something).
> Try it out and see if it avoids the crash.
Thanks! I just applied the patch to the 26.1 release source tree (it
applied cleanly) and rebuilt Emacs. This build still hangs, but
there's one difference: it no longer prints "Fatal error 11:
Segmentation fault" immediately after forking. When I sigint the Emacs
process after the hang, it still prints the NSAutoreleasePool error
message, and it still requires a sigkill to avoid eating CPU.
Is there anything else I should try to help track this down before
going down the road of running 'git bisect'?
- bug#32338: 26.1; term.el broken on macOS, Noam Postavsky, 2018/09/19
- bug#32338: 26.1; term.el broken on macOS, Constantine Vetoshev, 2018/09/20
- bug#32338: 26.1; term.el broken on macOS, Noam Postavsky, 2018/09/20
- bug#32338: 26.1; term.el broken on macOS,
Constantine Vetoshev <=
- bug#32338: 26.1; term.el broken on macOS, Noam Postavsky, 2018/09/22
- bug#32338: 26.1; term.el broken on macOS, Eli Zaretskii, 2018/09/23
- bug#32338: 26.1; term.el broken on macOS, Constantine Vetoshev, 2018/09/29
- bug#32338: 26.1; term.el broken on macOS, Eli Zaretskii, 2018/09/30
- bug#32338: 26.1; term.el broken on macOS, Constantine Vetoshev, 2018/09/30
- bug#32338: 26.1; term.el broken on macOS, Eli Zaretskii, 2018/09/30
- bug#32338: 26.1; term.el broken on macOS, Alan Third, 2018/09/30