From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Kun Liu Newsgroups: gmane.emacs.bugs Subject: bug#70760: 29.3.50; core dumps when copy in other apps Date: Fri, 17 May 2024 17:34:14 -0700 Message-ID: References: <86wmoagigo.fsf@gnu.org> <86zft5e6yf.fsf@gnu.org> <86wmo8etca.fsf@gnu.org> <86r0egck5b.fsf@gnu.org> <87cyq0tb5w.fsf@gmx.de> <86le4cx3w2.fsf@gnu.org> <87le4be520.fsf@gmx.de> <87a5krdkq2.fsf@gmx.de> <87seyicduz.fsf@gmx.de> <8734qgz9t9.fsf@gmx.de> <86pltkfilr.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000006edfd00618afa1bc" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6818"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Michael Albinus , 70760@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat May 18 02:36:23 2024 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 1s883j-0001Yk-6A for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 18 May 2024 02:36:23 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1s883P-0008P6-1Z; Fri, 17 May 2024 20:36:03 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s883L-0008OQ-2J for bug-gnu-emacs@gnu.org; Fri, 17 May 2024 20:35:59 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1s883K-0007BY-Q9 for bug-gnu-emacs@gnu.org; Fri, 17 May 2024 20:35:58 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1s883N-0004FJ-Sy for bug-gnu-emacs@gnu.org; Fri, 17 May 2024 20:36:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Kun Liu Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 18 May 2024 00:36:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 70760 X-GNU-PR-Package: emacs Original-Received: via spool by 70760-submit@debbugs.gnu.org id=B70760.171599253916303 (code B ref 70760); Sat, 18 May 2024 00:36:01 +0000 Original-Received: (at 70760) by debbugs.gnu.org; 18 May 2024 00:35:39 +0000 Original-Received: from localhost ([127.0.0.1]:58107 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s8830-0004Er-FG for submit@debbugs.gnu.org; Fri, 17 May 2024 20:35:39 -0400 Original-Received: from mail-lj1-f176.google.com ([209.85.208.176]:53692) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s882y-0004Ef-Hs for 70760@debbugs.gnu.org; Fri, 17 May 2024 20:35:37 -0400 Original-Received: by mail-lj1-f176.google.com with SMTP id 38308e7fff4ca-2e6f51f9de4so14169781fa.3 for <70760@debbugs.gnu.org>; Fri, 17 May 2024 17:35:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1715992467; x=1716597267; darn=debbugs.gnu.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=tuMFPY3rfKjM6vAyvGK2NCw/t/8o9ZFWTXkKEE5URAo=; b=h7FKP83Ci37rz1WRThawEeNwyo1A1qVC8uCdgc/tcu3E5uBeGIX+EHEY/2QRowQ3ug Q6LYL7qfZtKycf8AFfnyY8CMSMTzSrZBOcZi1glNguqmNsGIRHB/rKf676rmHRKh62ql ImFKeXr5N1cdhVPlT4BoI0zQlox1z0IEJVMTnZ0Fvz1jtyfs1YMKRQ1dvuuFJhXrlBJE kgnvmXgQX77lyUpxtb8mhvCZ8ITLvQafrUOs+CoQRvNw/VwaTyWSwJLDuaxdehSkFVk7 N6LyaRyo0znHAFM/TD+sP91pRHCcuX4R61/L27y0YOCDTS8dcqZV9U5/Qs8svV4YZbba F6Ag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715992467; x=1716597267; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=tuMFPY3rfKjM6vAyvGK2NCw/t/8o9ZFWTXkKEE5URAo=; b=XSUOXFWTfpogBCllnOqkMSroe2tv8p+GKa5iEEB+VfJgc1MbwzWH4XXjvxQwMoRIr7 VemvW194WW+b1GWCuLMRsAqlAuaWoUKgXFNUkjGlm6gE6u3MEMqyhlpwTjZ6LGn5JE8i lkrQDpelmiN+sBkMSOnSuQo/U+Slcnbt4yLfrAGFLbCcCuXZrZHJH5vtkur3n4mA1HCn CjGekKUP26vQryNPYdmB4OCfHjo6jifVwBPnSYdomQU/Fc5w4WiMwr9ib2wtc5B3PGX7 UXhXP0gZpwiXZx8Ul39Q/K9IjE19eZpUdigGpr8l/DAiZpY+BJ6yogo+1ZxpXuyKILHS qUxQ== X-Forwarded-Encrypted: i=1; AJvYcCXa/0tUNkwT8TaDl581KCC5BGG0liQeKM5xRjscr2y9eiEPLIw6DWgPF4DOJ1KQcasql8O4BOweNBj/3Y6L25Q4wH/o8kI= X-Gm-Message-State: AOJu0Yw4taFaaoo90lINZ31hVw3z9cobNV5JQam3nFWpyD/7L9jis10h m0OF7cc6u/3b4CbCS6p3EWbYok4Onb855vyrcq1vEDV4hcfewy3SeGOyicVigsLSfhzA2gNKEyi GWgVSoJs9RMrltP0smOOmtsN+psM= X-Google-Smtp-Source: AGHT+IEhzjXF1io//YR+GafQbTF4YtpioQzhsKz0pi687Y3shLQRGvFcoQshAKzG3XyeoMg/+Oru8V0vyzClpqgAw8c= X-Received: by 2002:a2e:b0f3:0:b0:2e2:b2c7:e597 with SMTP id 38308e7fff4ca-2e51fc34439mr208891061fa.3.1715992467003; Fri, 17 May 2024 17:34:27 -0700 (PDT) In-Reply-To: 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-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:285271 Archived-At: --0000000000006edfd00618afa1bc Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Just a quick update: I went through my .emacs line by line and was able to find the culprit. After I commented out "(follow-mode t)", Emacs has been running fine for a few hours now. It appears the combination of org-mode, follow-mode in Emacs 27-30 running in a Debian 11/12 VM in VirtualBox 6/7 on a Windows 11 host, and a copy operation on the host, sometimes causes problems. Thank you, Eli and Michael, for your help. I really appreciate it. On Fri, May 17, 2024 at 1:43=E2=80=AFPM Kun Liu wrote: > I've tried various combinations of Debian11/12, Emacs 27/28/29/30, > native-compilation yes/no. This behavior seems to be always present. > > On the other hand, based on all the tests I have done, it appears that > this issue happens when org-mode is loaded. I will run more tests and > report back if I see it happen without org-mode. > > On Fri, May 17, 2024 at 10:34=E2=80=AFAM Eli Zaretskii wro= te: > >> > From: Michael Albinus >> > Cc: Eli Zaretskii , 70760@debbugs.gnu.org >> > Date: Fri, 17 May 2024 18:23:46 +0200 >> > >> > But what if an event is added to the input event queue, which has an >> > arbitrary format? Or an existing event has been modified? It could loo= k >> > like a D-Bus event (the car of the event is `dbus-event'), but the res= t >> > of the list is random. It must not come via the dbusevent.c mechanism >> > I've explained above, anybody can push such an event onto then input >> > event queue. But I have no idea how to debug this. >> >> Which file descriptors do we listen to, apart of sub-processes and >> inotify? >> > --0000000000006edfd00618afa1bc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Just a quick update: I went through my .emacs line by line= and was able to find the culprit.

After I commented out= "(follow-mode t)", Emacs has been running=C2=A0fine for a few ho= urs now.

It appears the combination of org-mode, f= ollow-mode in Emacs 27-30 running in a Debian 11/12 VM=C2=A0in VirtualBox 6= /7 on a Windows 11 host, and a copy operation on the host, sometimes causes= problems.

Thank you, Eli and Michael, for your he= lp. I really appreciate it.

On Fri, May 17, 2024 at 1:43=E2=80=AFPM Ku= n Liu <kun.liu@gmail.com> wr= ote:
I've tried various combinations of Debian11/12, Emacs 27/28/29/30= , native-compilation yes/no. This behavior seems to be always present.
=
On the other hand, based on all the tests I have done, it ap= pears that this issue happens when org-mode is loaded. I will run more test= s and report back if I see it happen without org-mode.

On Fri, May 17,= 2024 at 10:34=E2=80=AFAM Eli Zaretskii <eliz@gnu.org> wrote:
> From: Michael Albinus <michael.albinus@gmx.de= >
> Cc: Eli Zaretskii <eliz@gnu.org>,=C2=A0 70760@debbugs.gnu.org
> Date: Fri, 17 May 2024 18:23:46 +0200
>
> But what if an event is added to the input event queue, which has an > arbitrary format? Or an existing event has been modified? It could loo= k
> like a D-Bus event (the car of the event is `dbus-event'), but the= rest
> of the list is random. It must not come via the dbusevent.c mechanism<= br> > I've explained above, anybody can push such an event onto then inp= ut
> event queue. But I have no idea how to debug this.

Which file descriptors do we listen to, apart of sub-processes and
inotify?
--0000000000006edfd00618afa1bc--