From: Kun Liu <kun.liu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Michael Albinus <michael.albinus@gmx.de>, 70760@debbugs.gnu.org
Subject: bug#70760: 29.3.50; core dumps when copy in other apps
Date: Fri, 17 May 2024 13:43:36 -0700 [thread overview]
Message-ID: <CA+Nei8M1-H5_9A3MUWcQaryewqTwzbrjjp5wyfHbJ_iSEcT-Jw@mail.gmail.com> (raw)
In-Reply-To: <86pltkfilr.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1092 bytes --]
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 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Michael Albinus <michael.albinus@gmx.de>
> > Cc: Eli Zaretskii <eliz@gnu.org>, 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 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?
>
[-- Attachment #2: Type: text/html, Size: 1628 bytes --]
next prev parent reply other threads:[~2024-05-17 20:43 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 [this message]
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
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+Nei8M1-H5_9A3MUWcQaryewqTwzbrjjp5wyfHbJ_iSEcT-Jw@mail.gmail.com \
--to=kun.liu@gmail.com \
--cc=70760@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).