From: Matt Bisson <bisson.m@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 49253@debbugs.gnu.org
Subject: bug#49253: 27.2; Emacs non-responsive when pasting into terminal-mode
Date: Mon, 28 Jun 2021 14:11:56 -0400 [thread overview]
Message-ID: <CAFbUcw+=CGuyQAmz581SmM2mTaA6dqs6vHX29H54Jq=XRjULaQ@mail.gmail.com> (raw)
In-Reply-To: <83tulhoon5.fsf@gnu.org>
> Some input Emacs gets fed at startup, which it doesn't expect, and
> which looks like a beginning of a paste sequence? This does happen
> right at startup, yes?
No. (Unless I'm misunderstanding what you're asking) the problem can
occur at any time. It's in response to simply pasting from the
clipboard into a terminal application. I can start Emacs, run for
days normally -- using terminal-mode, editing files, and so forth.
The second I go into the terminal-mode buffer and paste from the
(Windows, Mac, whatever) clipboard (NOT using the Emacs yank command),
the problem happens. If I never paste from the windowing system into
my terminal emulator, there are not problems, but invariably I find
some huge chunk of text, go to paste it into Emacs, and forget that
this will be a problem, and everything locks up irreversibly. It is
as if there is some race with multiple parties asking for select(),
but I don't know the Emacs threading model yet. TBH, I assumed it was
kind of single-threaded. :)
If your statement is more that the beginning of the sequence retrieved
from the xterm paste incantation occurs "at the start", then for that
I will have to debug into GDB, as we talked about.
> No, it's the other way around: you start Emacs from GDB. There are
> some instructions in etc/DEBUG.
Yes, I do know that's what you mean :) but it's not as if Emacs is
going to crash, and stop in the debugger. So my question is
basically, what src/*.c line should I set a breakpoint on to observe
the thing you would like me to observe? If you can't say, that's
perfectly reasonable. That said, as I type this, I can try to
interrupt Emacs when it's hung and see anything that's going on, but I
believe it will be after the problematic event has occurred.
On Mon, Jun 28, 2021 at 2:00 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Matt Bisson <bisson.m@gmail.com>
> > Date: Mon, 28 Jun 2021 13:30:19 -0400
> > Cc: 49253@debbugs.gnu.org
> >
> > Looking at the (E-Lisp) function, it's not obvious to me where I
> > should put a (native-code) breakpoint. Any thought? Of course I can
> > figure something out, but if you happen to know...
>
> No, it's the other way around: you start Emacs from GDB. There are
> some instructions in etc/DEBUG.
next prev parent reply other threads:[~2021-06-28 18:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 14:28 bug#49253: 27.2; Emacs non-responsive when pasting into terminal-mode Matt Bisson
2021-06-28 16:57 ` Eli Zaretskii
2021-06-28 17:18 ` Matt Bisson
2021-06-28 17:27 ` Eli Zaretskii
2021-06-28 17:30 ` Matt Bisson
2021-06-28 17:34 ` Matt Bisson
2021-06-28 17:59 ` Eli Zaretskii
2021-06-28 18:00 ` Eli Zaretskii
2021-06-28 18:11 ` Matt Bisson [this message]
2021-06-28 18:37 ` Eli Zaretskii
2021-06-28 20:09 ` Matt Bisson
2021-06-29 12:09 ` Eli Zaretskii
2021-06-29 15:06 ` Matt Bisson
2022-07-16 12:21 ` Lars Ingebrigtsen
2022-07-16 19:13 ` Matt Bisson
2023-12-08 19:06 ` Matt Bisson
2023-12-08 20:35 ` Matt Bisson
2023-12-09 11:10 ` Eli Zaretskii
2023-12-09 21:38 ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-11 16:10 ` Matt Bisson
2023-12-11 22:13 ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-13 19:26 ` Matt Bisson
2023-12-16 12:46 ` Eli Zaretskii
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='CAFbUcw+=CGuyQAmz581SmM2mTaA6dqs6vHX29H54Jq=XRjULaQ@mail.gmail.com' \
--to=bisson.m@gmail.com \
--cc=49253@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).