From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Matt Bisson Newsgroups: gmane.emacs.bugs Subject: bug#49253: 27.2; Emacs non-responsive when pasting into terminal-mode Date: Mon, 28 Jun 2021 14:11:56 -0400 Message-ID: References: <83zgvand0j.fsf@gnu.org> <83wnqdoq6t.fsf@gnu.org> <83tulhoon5.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4810"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 49253@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Jun 28 20:13:11 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lxvks-000144-Tx for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 28 Jun 2021 20:13:10 +0200 Original-Received: from localhost ([::1]:46696 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lxvkr-0003jb-RW for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 28 Jun 2021 14:13:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:45802) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lxvkk-0003hX-Gq for bug-gnu-emacs@gnu.org; Mon, 28 Jun 2021 14:13:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:40928) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1lxvkk-0007jj-84 for bug-gnu-emacs@gnu.org; Mon, 28 Jun 2021 14:13:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1lxvkj-0008Vw-T2 for bug-gnu-emacs@gnu.org; Mon, 28 Jun 2021 14:13:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Matt Bisson Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 28 Jun 2021 18:13:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 49253 X-GNU-PR-Package: emacs Original-Received: via spool by 49253-submit@debbugs.gnu.org id=B49253.162490393832678 (code B ref 49253); Mon, 28 Jun 2021 18:13:01 +0000 Original-Received: (at 49253) by debbugs.gnu.org; 28 Jun 2021 18:12:18 +0000 Original-Received: from localhost ([127.0.0.1]:52474 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lxvk2-0008V0-BJ for submit@debbugs.gnu.org; Mon, 28 Jun 2021 14:12:18 -0400 Original-Received: from mail-lf1-f41.google.com ([209.85.167.41]:38747) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1lxvjy-0008Uk-27 for 49253@debbugs.gnu.org; Mon, 28 Jun 2021 14:12:17 -0400 Original-Received: by mail-lf1-f41.google.com with SMTP id w19so5639733lfk.5 for <49253@debbugs.gnu.org>; Mon, 28 Jun 2021 11:12:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=SUrrXjX6strQct2oEbORCvjWLVVLV07h6kqv01XNeQw=; b=EeUozzBkffnLu7JDBFg6GV4C1z0F1Eu1r03y2MNLXF25TXd7ZmJd4E1LMU+WGB0OPs JopIy46EniYX49HinzxJaEzxneovqbwFlmOTiApc/FvdGmgkLokTRNNBfwFTzCKUyCWm Zs48Aymf0VJAJi7zAHa9rq3GhUfmiJ3fk3ROfteAnwYPivj9E2rb+rOFTBOuOIYG6ErI 0ewx3p7ELJmTbTNp8Vw+uz8NeqkBvrPmM+Mj7IZ+wE64I8ld8PmLxx6LIYM/xPeWQ46R wKc5T1DMaxhq07G64IaPYJysi3hR5P2X/QXIqcFLM1kIxyJ1zCEiKC+bs/F5pPvhS7OH W4cQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=SUrrXjX6strQct2oEbORCvjWLVVLV07h6kqv01XNeQw=; b=T+JNBoQ0ndP/FmZrqSn4YcxaP0QsSmSzKJATjzT+vaW2gQq22Iy7qWQAnYn+A1qFvk HJN4NlOhYbFVjsKma/sMYUNPnFzSdLkeRP0WVp5KqwOI5zden3v21ujk+cEvRmb907kn uddC45swNbd60sCDemxMAHh6e+me7zin2xRXjwdySJSHBcyjdz4S050I1y0EY68q+P7W 00anbamnyivxCg6Gi2FzyuvydfI5++rZqdn0mFKfjRLMHu9HjAP3Rzt2dncQl8pFPFXV 4OCXxLK+OXshf7YLh+exMV8H4bkHe5b9hF6FdZvGXkb+b/vLv6qdExWGrYtpzec4QXj6 oUOg== X-Gm-Message-State: AOAM531BD86RYavJHPfCCD5AW6uJ6jBnIhpo6S6Gee6lvcpF06Kg3Qdf UK3QLNSc8RGkLvdmD3O/g3dNszA5U0lO29mMo1w6Vj1aIsM= X-Google-Smtp-Source: ABdhPJzu2jbAKL/iXu3wBouXBT0jqzemUeYgX4mfUp/cu3oZ/mkZbPHKXN7KfoEhZevUZS9VmbQ/UxxHmuuNiH6uHNA= X-Received: by 2002:a19:ae11:: with SMTP id f17mr19567538lfc.198.1624903927894; Mon, 28 Jun 2021 11:12:07 -0700 (PDT) In-Reply-To: <83tulhoon5.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:209076 Archived-At: > 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 wrote: > > > From: Matt Bisson > > 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.