From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: kun.liu@gmail.com, 70760@debbugs.gnu.org
Subject: bug#70760: 29.3.50; core dumps when copy in other apps
Date: Sat, 18 May 2024 14:44:08 +0300 [thread overview]
Message-ID: <8634qfe453.fsf@gnu.org> (raw)
In-Reply-To: <87ttivxveq.fsf@gmx.de> (message from Michael Albinus on Sat, 18 May 2024 12:32:29 +0200)
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: kun.liu@gmail.com, 70760@debbugs.gnu.org
> Date: Sat, 18 May 2024 12:32:29 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> Hi Eli,
>
> >> 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 look
> >> 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
> >> 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?
>
> See xd_add_watch. xd_find_watch_fd returns the file descriptor
> reponsible for a given D-Bus connection (this is a bus like the system
> bus, the session bus, or a private bus). This file descriptor is added
> to Emacs via add_write_fd and add_read_fd, using the callback
> xd_read_queued_messages. So it might look like a subprocess ...
You are saying that output of some subprocess could be interpreted as
D-Bus event? How do we know which inputs to try to interpret as D-Bus
events? IOW, can you hypothesize how could we take some non-D-Bus
input and end up interpreting it as D-Bus?
next prev parent reply other threads:[~2024-05-18 11:44 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 21:30 bug#70760: 29.3.50; core dumps when copy in other apps Kun Liu
2024-05-04 7:11 ` Eli Zaretskii
2024-05-04 18:08 ` Kun Liu
2024-05-04 19:02 ` Eli Zaretskii
[not found] ` <CA+Nei8PsdEL-bOOQg86aZk1n1ahpb38XUokyHR98muaRTUY+5Q@mail.gmail.com>
2024-05-04 21:37 ` Kun Liu
2024-05-05 5:11 ` Eli Zaretskii
2024-05-05 15:45 ` Kun Liu
2024-05-05 16:12 ` Eli Zaretskii
2024-05-05 16:44 ` Kun Liu
2024-05-05 17:11 ` Kun Liu
2024-05-05 17:34 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-14 6:17 ` Kun Liu
2024-05-14 7:13 ` Eli Zaretskii
2024-05-15 10:35 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-15 16:27 ` Kun Liu
2024-05-15 17:54 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-15 18:25 ` Kun Liu
2024-05-15 21:06 ` Kun Liu
2024-05-16 9:20 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-16 19:07 ` Kun Liu
2024-05-17 16:23 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-17 17:34 ` Eli Zaretskii
2024-05-17 20:43 ` Kun Liu
2024-05-18 0:34 ` Kun Liu
2024-05-18 10:32 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-18 11:44 ` Eli Zaretskii [this message]
2024-05-18 11:54 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-18 12:09 ` Eli Zaretskii
2024-05-18 16:55 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-18 17:54 ` Eli Zaretskii
2024-05-18 18:22 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-18 19:20 ` Eli Zaretskii
2024-05-16 9:07 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8634qfe453.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=70760@debbugs.gnu.org \
--cc=kun.liu@gmail.com \
--cc=michael.albinus@gmx.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.