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: Thu, 16 May 2024 12:07: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> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000001a5745061896f284" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26703"; 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 Thu May 16 21:09:24 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 1s7gTj-0006dr-0I for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 16 May 2024 21:09:23 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1s7gTM-0004T0-TM; Thu, 16 May 2024 15:09:00 -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 1s7gTL-0004Sq-Ru for bug-gnu-emacs@gnu.org; Thu, 16 May 2024 15:08: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 1s7gTL-0001M4-Id for bug-gnu-emacs@gnu.org; Thu, 16 May 2024 15:08:59 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1s7gTN-0002aA-T3 for bug-gnu-emacs@gnu.org; Thu, 16 May 2024 15:09: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: Thu, 16 May 2024 19:09: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.17158865189910 (code B ref 70760); Thu, 16 May 2024 19:09:01 +0000 Original-Received: (at 70760) by debbugs.gnu.org; 16 May 2024 19:08:38 +0000 Original-Received: from localhost ([127.0.0.1]:50448 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7gSz-0002Zm-PM for submit@debbugs.gnu.org; Thu, 16 May 2024 15:08:38 -0400 Original-Received: from mail-lj1-f176.google.com ([209.85.208.176]:61773) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1s7gSw-0002Ze-UK for 70760@debbugs.gnu.org; Thu, 16 May 2024 15:08:36 -0400 Original-Received: by mail-lj1-f176.google.com with SMTP id 38308e7fff4ca-2e09138a2b1so16075991fa.3 for <70760@debbugs.gnu.org>; Thu, 16 May 2024 12:08:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1715886446; x=1716491246; 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=M40b58Z9fhkWXEwqlYjQjNhnai9ncciiyNSd34y0450=; b=MOoO333SF1nJCNXB83UD2WTxuerY6NkTnQgr67FlVp9BQGEWIIQCxFOQArSFzWtPcD A2VZLZ54tf1Jt7Wp89g1+kYaYH6SLdx6kbJAo6IHRj4XaDnrOalqiIqjOBHViUfWPoUw kbP/Wxqeqb3HmfmSKzvX9yUEw3rGvDKiTlQwHy77Bxr2rwJrJ6yC95VUMLiBY+UXu6Lh 1XLvzJWqbceXrRXbZoj0jaQ3HptjDwIf0BmlIvRNNaSH7b/BGNpTTr7MEcRgoFv1hbYV Gs9+oEhJP/5g7t9tlh5dENKM3zAiNMqrxLq+FHLzkVVDFwhqRZZ+rt/s7GJlOJv88G71 62CA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715886446; x=1716491246; 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=M40b58Z9fhkWXEwqlYjQjNhnai9ncciiyNSd34y0450=; b=LSBBobvfgd/XLRurNl4wJkMzr28nI7rnn5hBhli/0ly91XAXm+22VTXeYoOgjIVDES RbhUMKK6CeA/IEe3suGyS02AZzaPRTdtxK9fYV3y5yRgTbmcO5SvLgu7AbCgtMjYGIX/ i+5hrISHKY0ZOrjZ42bKLndK93OZJSYsptvCox0dXPLDAbjdb98TgQP5iMYjhAwumQfh tnSETg6xA+UBstksIUymi4l9jcLzdGgAaJwctfTPtqTB/PxUfexEJVia3k76WKbopkLW Pr56oZv3RpL5HMzXGfzlQBmYH9bkssxZw8zUIbn6qEWv9ljBjyPe8DskTm/hXU7UWauy y9lA== X-Forwarded-Encrypted: i=1; AJvYcCUC9/XMJzV3BD0E/t6LvK2UiEB+ydKRYoyt+M/1OuSC6W6DG90LZOF+yT03I4ZYgu7SQjSd20e1vFrTSHc2irgfCcm8u6Y= X-Gm-Message-State: AOJu0Ywtt3TEUcjquXYEbSROsk80CfMRYqu0QNgOfoA5HtK9ZI3q39V2 adYI6I6pqXtOSiA9EBP/fj+IX8u0Qt7pLjlghkJetDDo9cRBNdBfgB9f08miCyL8bS9imvWAp/5 eIQcgdOFuBauNpjvw4I49JXXcQNYvIz+c X-Google-Smtp-Source: AGHT+IHXQhy6v+9JKliu3Ee1tiuPGtBxmy7trU9XjM83TfP+JiobWIBJNMaBfLqVGZKhim+Sd9ucLPhgIStrwu90fZ4= X-Received: by 2002:a2e:be9c:0:b0:2dc:b04b:b3c0 with SMTP id 38308e7fff4ca-2e51fe52160mr165083721fa.6.1715886446235; Thu, 16 May 2024 12:07:26 -0700 (PDT) In-Reply-To: <87seyicduz.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:285191 Archived-At: --0000000000001a5745061896f284 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks much, Michael, for the detailed explanation. I spent more time on this issue. I watched closely both "dbus-monitor --system" and "dbus-monitor" outputs, while trying to replicate the issue in Emacs. It appears that just as you said, when Emacs reported invalid dbus events, which crashes Emacs sometimes, dbus-monitor outputs never showed any messages immediately preceding or following the error. Which really begs the question, if dbus did not have any messages for Emacs at the time, why did Emacs think there was a message for it? On Thu, May 16, 2024 at 2:20=E2=80=AFAM Michael Albinus wrote: > Kun Liu writes: > > Hi, > > > I started dbus-monitor to monitor both session and system messages. > > Then I repeated the test mentioned in the last message. > > > > The relevant lines in the "dbus-monitor --system" output: (please note > > that the dbus address is different from the previous test) > > Yep. Emacs gets a new D-Bus address every new start, it is :1.82 this > case. > > > method call time=3D1715806663.121956 sender=3D:1.82 -> > > destination=3Dorg.freedesktop.DBus serial=3D1 path=3D/org/freedesktop/D= Bus; > > interface=3Dorg.freedesktop.DBus; member=3DHello > > method return time=3D1715806663.121973 sender=3Dorg.freedesktop.DBus -> > > destination=3D:1.82 serial=3D1 reply_serial=3D1 > > string ":1.82" > > Emacs sys "Hello" to D-Bus. > > > signal time=3D1715806663.121976 sender=3Dorg.freedesktop.DBus -> > > destination=3D(null destination) serial=3D101 path=3D/org/freedesktop/D= Bus; > > interface=3Dorg.freedesktop.DBus; member=3DNameOwnerChanged > > string ":1.82" > > string "" > > string ":1.82" > > signal time=3D1715806663.121981 sender=3Dorg.freedesktop.DBus -> > > destination=3D:1.82 serial=3D2 path=3D/org/freedesktop/DBus; > > interface=3Dorg.freedesktop.DBus; member=3DNameAcquired > > string ":1.82" > > D-Bus replies two signals, saying that it understood the "Hello", and > that it has registered the service with unique name :1.82. > > > method call time=3D1715806663.130182 sender=3D:1.82 -> > > destination=3Dorg.freedesktop.DBus serial=3D2 path=3D/org/freedesktop/D= Bus; > > interface=3Dorg.freedesktop.DBus; member=3DAddMatch > > string > > > "type=3D'signal',interface=3D'org.freedesktop.DBus.Local',member=3D'Disco= nnected',path=3D'/org/freedesktop/DBus/Local'" > > > > method return time=3D1715806663.130202 sender=3Dorg.freedesktop.DBus -> > > destination=3D:1.82 serial=3D3 reply_serial=3D2 > > Emacs registers for signals. > > > ... > > signal time=3D1715806675.545929 sender=3Dorg.freedesktop.DBus -> > > destination=3D:1.82 serial=3D4 path=3D/org/freedesktop/DBus; > > interface=3Dorg.freedesktop.DBus; member=3DNameLost > > string ":1.82" > > signal time=3D1715806675.545978 sender=3Dorg.freedesktop.DBus -> > > destination=3D(null destination) serial=3D102 path=3D/org/freedesktop/D= Bus; > > interface=3Dorg.freedesktop.DBus; member=3DNameOwnerChanged > > string ":1.82" > > string ":1.82" > > string "" > > This is very likely the time you have stopped Emacs, and D-Bus > unregisters its unique name, therefore. > > > The relevant lines in the "dbus-monitor" output: > > The look very similar to the system bus output. Here, Emacs has the > unique name :1.177. > > > method call time=3D1715806663.132256 sender=3D:1.153 -> > > destination=3Dorg.freedesktop.DBus serial=3D657 > > path=3D/org/freedesktop/DBus; interface=3Dorg.freedesktop.DBus; > > member=3DGetConnectionUnixProcessID > > string ":1.177" > > This is an additional call from service 1.153, which wants to know the > Emacs pid. We can ignore it. > > Everything normal, and not related to the problem I believe. > > Best regards, Michael. > --0000000000001a5745061896f284 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks much, Michael, for the detailed explanation.
I spent more time on this issue. I watched closely both "dbus-m= onitor --system" and "dbus-monitor" outputs, while trying to= replicate the issue in Emacs. It appears that just as you said, when Emacs= reported invalid dbus events, which crashes Emacs sometimes, dbus-monitor = outputs never showed any messages immediately preceding=C2=A0or following t= he error.

Which really begs the question, if dbus = did not have any messages for Emacs at the time, why did Emacs think there = was a message for it?

On Thu, May 16, 2024 at 2:20=E2=80=AFAM Mi= chael Albinus <michael.albinus= @gmx.de> wrote:
Kun Liu <k= un.liu@gmail.com> writes:

Hi,

> I started dbus-monitor to monitor both session and system messages. > Then I repeated the test mentioned in the last message.
>
> The relevant lines in the "dbus-monitor --system" output: (p= lease note
> that the dbus address is different from the previous test)

Yep. Emacs gets a new D-Bus address every new start, it is :1.82 this
case.

> method call time=3D1715806663.121956 sender=3D:1.82 ->
> destination=3Dorg.freedesktop.DBus serial=3D1 path=3D/org/freedesktop/= DBus;
> interface=3Dorg.freedesktop.DBus; member=3DHello
> method return time=3D1715806663.121973 sender=3Dorg.freedesktop.DBus -= >
> destination=3D:1.82 serial=3D1 reply_serial=3D1
>=C2=A0 =C2=A0 string ":1.82"

Emacs sys "Hello" to D-Bus.

> signal time=3D1715806663.121976 sender=3Dorg.freedesktop.DBus -> > destination=3D(null destination) serial=3D101 path=3D/org/freedesktop/= DBus;
> interface=3Dorg.freedesktop.DBus; member=3DNameOwnerChanged
>=C2=A0 =C2=A0 string ":1.82"
>=C2=A0 =C2=A0 string ""
>=C2=A0 =C2=A0 string ":1.82"
> signal time=3D1715806663.121981 sender=3Dorg.freedesktop.DBus -> > destination=3D:1.82 serial=3D2 path=3D/org/freedesktop/DBus;
> interface=3Dorg.freedesktop.DBus; member=3DNameAcquired
>=C2=A0 =C2=A0 string ":1.82"

D-Bus replies two signals, saying that it understood the "Hello",= and
that it has registered the service with unique name :1.82.

> method call time=3D1715806663.130182 sender=3D:1.82 ->
> destination=3Dorg.freedesktop.DBus serial=3D2 path=3D/org/freedesktop/= DBus;
> interface=3Dorg.freedesktop.DBus; member=3DAddMatch
>=C2=A0 =C2=A0 string
> "type=3D'signal',interface=3D'org.freedesktop.DBus.Lo= cal',member=3D'Disconnected',path=3D'/org/freedesktop/DBus/= Local'"
>
> method return time=3D1715806663.130202 sender=3Dorg.freedesktop.DBus -= >
> destination=3D:1.82 serial=3D3 reply_serial=3D2

Emacs registers for signals.

> ...
> signal time=3D1715806675.545929 sender=3Dorg.freedesktop.DBus -> > destination=3D:1.82 serial=3D4 path=3D/org/freedesktop/DBus;
> interface=3Dorg.freedesktop.DBus; member=3DNameLost
>=C2=A0 =C2=A0 string ":1.82"
> signal time=3D1715806675.545978 sender=3Dorg.freedesktop.DBus -> > destination=3D(null destination) serial=3D102 path=3D/org/freedesktop/= DBus;
> interface=3Dorg.freedesktop.DBus; member=3DNameOwnerChanged
>=C2=A0 =C2=A0 string ":1.82"
>=C2=A0 =C2=A0 string ":1.82"
>=C2=A0 =C2=A0 string ""

This is very likely the time you have stopped Emacs, and D-Bus
unregisters its unique name, therefore.

> The relevant lines in the "dbus-monitor" output:

The look very similar to the system bus output. Here, Emacs has the
unique name :1.177.

> method call time=3D1715806663.132256 sender=3D:1.153 ->
> destination=3Dorg.freedesktop.DBus serial=3D657
> path=3D/org/freedesktop/DBus; interface=3Dorg.freedesktop.DBus;
> member=3DGetConnectionUnixProcessID
>=C2=A0 =C2=A0 string ":1.177"

This is an additional call from service 1.153, which wants to know the
Emacs pid. We can ignore it.

Everything normal, and not related to the problem I believe.

Best regards, Michael.
--0000000000001a5745061896f284--