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: Wed, 15 May 2024 09:27:15 -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> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000004befed0618809800" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="16254"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , 70760@debbugs.gnu.org To: Michael Albinus Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed May 15 18:29: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 1s7HVJ-0003zw-R8 for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 15 May 2024 18:29:21 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1s7HUz-00087t-Ux; Wed, 15 May 2024 12:29:02 -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 1s7HUy-00081O-9c for bug-gnu-emacs@gnu.org; Wed, 15 May 2024 12:29:00 -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 1s7HUy-0002L2-0g for bug-gnu-emacs@gnu.org; Wed, 15 May 2024 12:29:00 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1s7HUz-000404-Kx for bug-gnu-emacs@gnu.org; Wed, 15 May 2024 12:29: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: Wed, 15 May 2024 16:29: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.171579052215366 (code B ref 70760); Wed, 15 May 2024 16:29:01 +0000 Original-Received: (at 70760) by debbugs.gnu.org; 15 May 2024 16:28:42 +0000 Original-Received: from localhost ([127.0.0.1]:42997 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7HUf-0003zm-Mw for submit@debbugs.gnu.org; Wed, 15 May 2024 12:28:42 -0400 Original-Received: from mail-lj1-f169.google.com ([209.85.208.169]:47133) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7HUc-0003zc-II for 70760@debbugs.gnu.org; Wed, 15 May 2024 12:28:39 -0400 Original-Received: by mail-lj1-f169.google.com with SMTP id 38308e7fff4ca-2e34e85ebf4so64512791fa.2 for <70760@debbugs.gnu.org>; Wed, 15 May 2024 09:28:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1715790450; x=1716395250; 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=kKk2a7kxbNLRBrWHbrcswngpES8eJ8YgFjp71MfTChk=; b=AlTHlUFOIpPUU9YR8sv8/aECDUb2e9ZT2ioNZ8CeVqvjpKPaYKCJg0eGzWWf874z/d aJTd045WDrdRZe3GEtAc8BZDN5OfA06YpeyompbjirVnutHeCuyO3CLrfFh5wbu+kqlq 6E1+xOah/zRTSU/iWpzq4J1qyzSdTlEzs5NOB/eqliyf4PbpfVicV9tYDdKpLbBT/6Uk iowBHyp8ZB7RdnmsjJ6zZffiT3d3mBw1445/EzOpZaShFil5Q9RSRy498uWZCrdp7aUS sgKNN+0A1uiqDLEtoFvVyT1fXqSmaKaDHJty2OcJYvSHJGIZw8Hl5392dfdPNfLYrWhf 3DNQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715790450; x=1716395250; 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=kKk2a7kxbNLRBrWHbrcswngpES8eJ8YgFjp71MfTChk=; b=cIaEd4behPObAekqxiVy/bh+NFU4ilWYtSllnTBncNCMWFdR0WC8xNX45sbXu99sCn W/1XRQhs20T85Qcf7ZtDj7wOJTFQNWJ3LNn8bF8jShKJEYHZsPojAc82RbmTm0ur7NiD 8wCZB2C+6b9PFunvHUVcU++hllkQJ19Zc9wlmJY2RAb9lhYmcyaksH4bt1tLIM+RDPcb gMUS2ypWhjUuCQYj5FuiqCbKYo4vKlFEYjx+1SlLBlA8P4aowSpzsmEyA4buDvaO8Are 9cWJBMKpVcgzuCd3NtpU2FQcAfigFtoezDk8WNiIuJmodo2TZYsdcBWzkiSVXYB7Mikw MR/Q== X-Forwarded-Encrypted: i=1; AJvYcCVsZZbMN3p6xXyCQYoS/7pOCKQnGTfMepFTelQVy42yyyQnge1jBaVa+IzHnRLAAvYozJ8LaLtTd+mIoaRzag3OQNNLpA0= X-Gm-Message-State: AOJu0Yw/vpr3yPMOAoGtYnU3kwH1+JXf8z2Xah6BnkJ27GJwVw1OwFij BTLO1SjCX/B9bt+cTDawe3Y4DSa95qG+MjQvzNijONSfKScDj3W33GRRs2Yl8SwfNvx6dvzi8Fj mCRaSar8ua68lPCXpBEKCnLlEcMU= X-Google-Smtp-Source: AGHT+IEFB6tGiAizExLr30/MMouMMYyk53lpesMLIf+gsFoB6xj1uzChgPQmdPpwCayyalwa3m3FI/TBijjyys+2WDE= X-Received: by 2002:a2e:3a0f:0:b0:2e0:37be:b70f with SMTP id 38308e7fff4ca-2e51fe57d31mr97195261fa.26.1715790450255; Wed, 15 May 2024 09:27:30 -0700 (PDT) In-Reply-To: <87le4be520.fsf@gmx.de> 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:285096 Archived-At: --0000000000004befed0618809800 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I did as instructed. Here is a couple of instances of what I saw in *Messages* right after I was able to trigger the problem. case 1: DBus-Event (dbus-event :post-blank 0 :post-affiliated 1455145 :mode nil :granularity element :cached t :parent (section (:begin 1179957 :end 1609350 :contents-begin 1179957 :contents-end 1609349 :robust-begin 1179957 :robust-end 1609347 :post-blank 1 :post-affiliated 1179957 :mode section :granularity element :cached t :parent (headline (:raw-value Old stuff :begin 1179945 :end 1609350 :pre-blank 0 :contents-begin 1179957 :contents-end 1609349 :robust-begin 1180109 :robust-end 1609347 :level 1 :priority nil :tags nil :todo-keyword nil :todo-type nil :post-blank 1 :footnote-section-p nil :archivedp nil :commentedp nil :post-affiliated 1179945 :ARCHIVE_TIME 2020-10-17 Sat 15:00 :ARCHIVE_FILE ~/work/worklog.org :ARCHIVE_OLPATH Scratch :ARCHIVE_CATEGORY worklog :title Old stuff :mode nil :granularity element :cached t :parent (org-data (:begin 1 :contents-begin 1 :contents-end 15432855 :end 15432856 :robust-begin 3 :robust-end 15432853 :post-blank 1 :post-affiliated 1 :path /home/kun/work/worklog.org_archive :mode org-data :CATEGORY worklog :cached t :org-element--cache-sync-key nil)) :org-element--cache-sync-key nil)) :org-element--cache-sync-key nil)) :org-element--cache-sync-key nil) [2 times] Entering debugger... DBus-Event (dbus-event x . make4ht) funcall-interactively: Wrong type argument: listp, "make4ht" case 2: DBus-Event (dbus-event :post-blank 0 :post-affiliated 1455145 :mode nil :granularity element :cached t :parent (section (:begin 1179957 :end 1609350 :contents-begin 1179957 :contents-end 1609349 :robust-begin 1179957 :robust-end 1609347 :post-blank 1 :post-affiliated 1179957 :mode section :granularity element :cached t :parent (headline (:raw-value Old stuff :begin 1179945 :end 1609350 :pre-blank 0 :contents-begin 1179957 :contents-end 1609349 :robust-begin 1180109 :robust-end 1609347 :level 1 :priority nil :tags nil :todo-keyword nil :todo-type nil :post-blank 1 :footnote-section-p nil :archivedp nil :commentedp nil :post-affiliated 1179945 :ARCHIVE_TIME 2020-10-17 Sat 15:00 :ARCHIVE_FILE ~/work/worklog.org :ARCHIVE_OLPATH Scratch :ARCHIVE_CATEGORY worklog :title Old stuff :mode nil :granularity element :cached t :parent (org-data (:begin 1 :contents-begin 1 :contents-end 15432855 :end 15432856 :robust-begin 3 :robust-end 15432853 :post-blank 1 :post-affiliated 1 :path /home/kun/work/worklog.org_archive :mode org-data :CATEGORY worklog :cached t :org-element--cache-sync-key nil)) :org-element--cache-sync-key nil)) :org-element--cache-sync-key nil)) :org-element--cache-sync-key nil) [2 times] dbus-event-bus-name: D-Bus error: "Not a valid D-Bus event", (dbus-event :post-blank 0 :post-affiliated 1455145 :mode nil :granularity element :cached ...) On Wed, May 15, 2024 at 3:35=E2=80=AFAM Michael Albinus wrote: > Eli Zaretskii writes: > > Hi, > > > We have already established that some invalid D-Bus events cause these > > problems. What we need now is to find out what kind of D-Bus events > > are those, and what does VirtualBox mean to happen when it emits these > > D-Bus events? > > > > Looking at dbus-check-event, I see that event of the form > > > > (dbus-event 10 14) > > > > is invalid because the first member of the list after 'dbus-event' > > should be either a keyword (a symbol, AFAIU) or a string, but here we > > have a number. > > > > The event > > > > (dbus-event "[ \11]*$") > > > > from your previous message is also invalid, since it has only one > > member after 'dbus-event'. > > > > IOW, VirtualBox is emitting invalid D-Bus events, at least as far as > > our support for D-Bus is concerned. > > > > Michael, are these events invalid according to the D-Bus spec, or we > > just lack support for them in Emacs? If the former, I don't see how > > this can be an Emacs problem; you should ask the VirtualBox folks what > > to do to avoid this. > > These aren't valid D-Bus events according to the spec, and I doubt that > they come from D-Bus itself. But let's instrument Emacs in order to see > which D-Bus events flow around. The following recipe: > > --8<---------------cut here---------------start------------->8--- > # rm src/dbusbind.o > # make MYCPPFLAGS=3D'-DDBUS_DEBUG' > # src/emacs --eval '(setq dbus-debug t message-log-max t)' > --8<---------------cut here---------------end--------------->8--- > > Then trigger the problem, and send us the *Messages* buffer afterwards. > Recompile Emacs w/o the MYCPPFLAGS arg. > > > Maybe we can make Emacs more tolerant to these issues, e.g., make the > > error a warning or a message? > > Maybe. But my gut feeling tells me there is an error in Emacs handling > incoming event. And this isn't related to D-Bus, necessarily. > > > All in all, I feel like this is not an Emacs issue at all, and should > > not be brought to us. > > Maybe. But I'd like to see the D-Bus events first. > > Best regards, Michael. > --0000000000004befed0618809800 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I did as instructed.

Here is a couple o= f instances of what I saw in *Messages* right after I was able to trigger t= he problem.

case 1:

DBus-= Event (dbus-event :post-blank 0 :post-affiliated 1455145 :mode nil :granula= rity element :cached t :parent (section (:begin 1179957 :end 1609350 :conte= nts-begin 1179957 :contents-end 1609349 :robust-begin 1179957 :robust-end 1= 609347 :post-blank 1 :post-affiliated 1179957 :mode section :granularity el= ement :cached t :parent (headline (:raw-value Old stuff :begin 1179945 :end= 1609350 :pre-blank 0 :contents-begin 1179957 :contents-end 1609349 :robust= -begin 1180109 :robust-end 1609347 :level 1 :priority nil :tags nil :todo-k= eyword nil :todo-type nil :post-blank 1 :footnote-section-p nil :archivedp = nil :commentedp nil :post-affiliated 1179945 :ARCHIVE_TIME 2020-10-17 Sat 1= 5:00 :ARCHIVE_FILE ~/work/worklog.org :A= RCHIVE_OLPATH Scratch :ARCHIVE_CATEGORY worklog :title Old stuff :mode nil = :granularity element :cached t :parent (org-data (:begin 1 :contents-begin = 1 :contents-end 15432855 :end 15432856 :robust-begin 3 :robust-end 15432853= :post-blank 1 :post-affiliated 1 :path /home/kun/work/worklog.org_archive = :mode org-data :CATEGORY worklog :cached t :org-element--cache-sync-key nil= )) :org-element--cache-sync-key nil)) :org-element--cache-sync-key nil)) :o= rg-element--cache-sync-key nil) [2 times]
Entering debugger...
DBus-E= vent (dbus-event x . make4ht)
funcall-interactively: Wrong type argument= : listp, "make4ht"

case 2:

DBus-Event (dbus-event :post-blank 0 :post-affiliated 14551= 45 :mode nil :granularity element :cached t :parent (section (:begin 117995= 7 :end 1609350 :contents-begin 1179957 :contents-end 1609349 :robust-begin = 1179957 :robust-end 1609347 :post-blank 1 :post-affiliated 1179957 :mode se= ction :granularity element :cached t :parent (headline (:raw-value Old stuf= f :begin 1179945 :end 1609350 :pre-blank 0 :contents-begin 1179957 :content= s-end 1609349 :robust-begin 1180109 :robust-end 1609347 :level 1 :priority = nil :tags nil :todo-keyword nil :todo-type nil :post-blank 1 :footnote-sect= ion-p nil :archivedp nil :commentedp nil :post-affiliated 1179945 :ARCHIVE_= TIME 2020-10-17 Sat 15:00 :ARCHIVE_FILE ~/work/worklog.org :ARCHIVE_OLPATH Scratch :ARCHIVE_CATEGORY worklog :title= Old stuff :mode nil :granularity element :cached t :parent (org-data (:beg= in 1 :contents-begin 1 :contents-end 15432855 :end 15432856 :robust-begin 3= :robust-end 15432853 :post-blank 1 :post-affiliated 1 :path /home/kun/work= /worklog.org_archive :mode org-data :CATEGORY worklog :cached t :org-elemen= t--cache-sync-key nil)) :org-element--cache-sync-key nil)) :org-element--ca= che-sync-key nil)) :org-element--cache-sync-key nil) [2 times]
dbus-even= t-bus-name: D-Bus error: "Not a valid D-Bus event", (dbus-event := post-blank 0 :post-affiliated 1455145 :mode nil :granularity element :cache= d ...)


On Wed, May 15, 2024 at 3:35=E2=80=AFAM Mich= ael Albinus <michael.albinus@g= mx.de> wrote:
Eli Zaretskii <el= iz@gnu.org> writes:

Hi,

> We have already established that some invalid D-Bus events cause these=
> problems.=C2=A0 What we need now is to find out what kind of D-Bus eve= nts
> are those, and what does VirtualBox mean to happen when it emits these=
> D-Bus events?
>
> Looking at dbus-check-event, I see that event of the form
>
>=C2=A0 =C2=A0(dbus-event 10 14)
>
> is invalid because the first member of the list after 'dbus-event&= #39;
> should be either a keyword (a symbol, AFAIU) or a string, but here we<= br> > have a number.
>
> The event
>
>=C2=A0 =C2=A0(dbus-event "[ \11]*$")
>
> from your previous message is also invalid, since it has only one
> member after 'dbus-event'.
>
> IOW, VirtualBox is emitting invalid D-Bus events, at least as far as > our support for D-Bus is concerned.
>
> Michael, are these events invalid according to the D-Bus spec, or we > just lack support for them in Emacs?=C2=A0 If the former, I don't = see how
> this can be an Emacs problem; you should ask the VirtualBox folks what=
> to do to avoid this.

These aren't valid D-Bus events according to the spec, and I doubt that=
they come from D-Bus itself. But let's instrument Emacs in order to see=
which D-Bus events flow around. The following recipe:

--8<---------------cut here---------------start------------->8---
# rm src/dbusbind.o
# make MYCPPFLAGS=3D'-DDBUS_DEBUG'
# src/emacs --eval '(setq dbus-debug t message-log-max t)'
--8<---------------cut here---------------end--------------->8---

Then trigger the problem, and send us the *Messages* buffer afterwards.
Recompile Emacs w/o the MYCPPFLAGS arg.

> Maybe we can make Emacs more tolerant to these issues, e.g., make the<= br> > error a warning or a message?

Maybe. But my gut feeling tells me there is an error in Emacs handling
incoming event. And this isn't related to D-Bus, necessarily.

> All in all, I feel like this is not an Emacs issue at all, and should<= br> > not be brought to us.

Maybe. But I'd like to see the D-Bus events first.

Best regards, Michael.
--0000000000004befed0618809800--