From: Constantine Vetoshev <vetoshev@gmail.com>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 32338@debbugs.gnu.org
Subject: bug#32338: 26.1; term.el broken on macOS
Date: Sat, 22 Sep 2018 11:12:15 -0700 [thread overview]
Message-ID: <CA+CaSqqV1-=+kf4NH2bj64pT860A4ZCaxr=d_6D-yzVhKezMTw@mail.gmail.com> (raw)
In-Reply-To: <87bm8rpu0x.fsf@gmail.com>
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'?
next prev parent reply other threads:[~2018-09-22 18:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 19:29 bug#32338: 26.1; term.el broken on macOS Constantine Vetoshev
2018-09-19 23:30 ` Noam Postavsky
2018-09-20 14:15 ` Constantine Vetoshev
2018-09-21 0:35 ` Noam Postavsky
2018-09-22 18:12 ` Constantine Vetoshev [this message]
2018-09-22 22:14 ` Noam Postavsky
2018-09-23 5:42 ` Eli Zaretskii
2018-09-29 23:52 ` Constantine Vetoshev
2018-09-30 5:59 ` Eli Zaretskii
2018-09-30 15:25 ` Constantine Vetoshev
2018-09-30 17:13 ` Eli Zaretskii
2018-10-02 22:51 ` Constantine Vetoshev
2018-10-03 14:59 ` Eli Zaretskii
2018-10-03 19:21 ` Constantine Vetoshev
2018-10-04 16:15 ` Eli Zaretskii
2018-09-30 9:16 ` Alan Third
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+CaSqqV1-=+kf4NH2bj64pT860A4ZCaxr=d_6D-yzVhKezMTw@mail.gmail.com' \
--to=vetoshev@gmail.com \
--cc=32338@debbugs.gnu.org \
--cc=npostavs@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).