From: Stefan Kangas <stefan@marxist.se>
To: Joseph Mingrone <jrm@ftfl.ca>
Cc: 14473@debbugs.gnu.org
Subject: bug#14473: 24.3; emacs locks up when eshell attempts to display a dialog
Date: Thu, 3 Oct 2019 18:48:02 +0200 [thread overview]
Message-ID: <CADwFkmmUkoyLixaktJLcBHVwuaOTw7mDCmgGZrKf+XGOC9cwOw@mail.gmail.com> (raw)
In-Reply-To: <86wodlakye.fsf@phe.ftfl.ca>
Joseph Mingrone <jrm@ftfl.ca> writes:
> It's still a problem (26.3 and 2019-09-15 master-branch build) in that the dialog is not displayed, but the Emacs process no longer consumes 100% CPU.
Thanks for reporting back.
> Here is a simple recipe to reproduce the problem. It assumes the FreeBSD ports tree is installed in the default location, which is /usr/ports.
Can you think of any way to reproduce this if you are not using
FreeBSD? Is there some particular command run by "make config" that
makes eshell freeze for example? It seems to me that very few Emacs
developers are using FreeBSD, and I personally don't have access to
any FreeBSD systems for debugging.
> Instead of the dialog displaying, eshell becomes unusable (blank screen and no keys will return the prompt). Trying to exit by hitting TAB/Enter reports
>
> Completion function pcomplete-completions-at-point uses a deprecated calling convention
> Warning: pcomplete-completions-at-point failed to return valid completion data!
>
> You can switch buffers and kill the eshell process now though.
What happens if you run M-x toggle-debug-on-error before trying to
reproduce? Do you then get a backtrace?
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2019-10-03 16:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-25 17:19 bug#14473: 24.3; emacs locks up when eshell attempts to display a dialog Joseph Mingrone
2019-09-30 15:47 ` Stefan Kangas
2019-09-30 16:10 ` Eli Zaretskii
2019-10-03 15:48 ` Joseph Mingrone
2019-10-03 16:48 ` Stefan Kangas [this message]
2019-10-07 18:53 ` Joseph Mingrone
2019-10-08 14:05 ` Stefan Kangas
2019-10-14 17:53 ` Joseph Mingrone
2019-10-14 19:34 ` Stefan Kangas
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=CADwFkmmUkoyLixaktJLcBHVwuaOTw7mDCmgGZrKf+XGOC9cwOw@mail.gmail.com \
--to=stefan@marxist.se \
--cc=14473@debbugs.gnu.org \
--cc=jrm@ftfl.ca \
/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).