unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: Constantine Vetoshev <vetoshev@gmail.com>
Cc: 32338@debbugs.gnu.org
Subject: bug#32338: 26.1; term.el broken on macOS
Date: Wed, 19 Sep 2018 19:30:41 -0400	[thread overview]
Message-ID: <87k1nhoyji.fsf@gmail.com> (raw)
In-Reply-To: <CA+CaSqpYLPHx8EXvjudNj4KMTa8coamwS=dSOtU0tzPw-iKt1w@mail.gmail.com> (Constantine Vetoshev's message of "Tue, 31 Jul 2018 15:29:21 -0400")

Constantine Vetoshev <vetoshev@gmail.com> writes:

> M-x term nor M-x ansi-term both cause Emacs to lock up on macOS
> 10.13.4. Steps to reproduce with -Q:
>
> 1. M-x ansi-term
> 2. Type in /bin/bash, hit Enter
>
> You'll notice that a prompt does not appear in the resulting window
> (*ansi-term* buffer). Hit Enter. Emacs will display "Writing to process:
> Input/output error, *ansi-term*" in the minibuffer. If you started Emacs
> from the terminal, it will display "Fatal error 4: Illegal
> instruction".

Do you mean Emacs itself is hitting this error and crashing, or
/bin/bash running inside *ansi-term* does?  Can you run under a debugger
and get a backtrace?

> After this, Emacs becomes unstable and will eventually
> stop responding to input. All this worked fine in 25.3 and earlier
> (i.e., a shell prompt appears and can be readily used).

Does it currently work fine on 25.3 (i.e., is it possible an OS update
caused this to stop working on earlier Emacs versions as well)?  If you
load term.el from 25.3 into 26.1 does it work then?

> In GNU Emacs 26.1 (build 1, x86_64-apple-darwin17.5.0, NS
> appkit-1561.40 Version 10.13.4 (Build 17E202))
>  of 2018-05-29 built on athena
> Windowing system distributor 'Apple', version 10.3.1561





  reply	other threads:[~2018-09-19 23:30 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 [this message]
2018-09-20 14:15   ` Constantine Vetoshev
2018-09-21  0:35     ` Noam Postavsky
2018-09-22 18:12       ` Constantine Vetoshev
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=87k1nhoyji.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --cc=32338@debbugs.gnu.org \
    --cc=vetoshev@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).