From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Bjoern Bidar <bjorn.bidar@thaodan.de>
Cc: 56967@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#56967: 29.0.50; Frequent crashes under Wayland
Date: Fri, 05 Aug 2022 08:50:39 +0800 [thread overview]
Message-ID: <878ro37bts.fsf@yahoo.com> (raw)
In-Reply-To: <16164156.Y83TkukXya@odin> (Bjoern Bidar's message of "Fri, 05 Aug 2022 03:18:17 +0300")
Bjoern Bidar <bjorn.bidar@thaodan.de> writes:
>> Eli Zaretskii <eliz@gnu.org> writes:
>
>> > Then please run Emacs under a debugger, or attach a debugger to it
>> > after you start it, and place a breakpoint in the function
>> > Fkill_emacs. When that breakpoint breaks, produce a backtrace (with
>> > the "thread apply all bt" command in GDB) and post that backtrace
>> > here.
>>
>> Please also place a breakpoint on _exit -- GDK always calls that with
>> the exit code 1 that when a display connection is abruptly lost, in
>> which case Fkill_emacs has no chance to run.
>>
>> Thanks in advance.
>
> Started emacs via systemd as and set both break points as asked.
>
> There you go:
>
>
> Thread 1 "emacs" hit Breakpoint 2, __GI__exit (status=status@entry=1) at ../
> sysdeps/unix/sysv/linux/_exit.c:27
> 27 {
> (gdb) bt
> #0 __GI__exit (status=status@entry=1) at ../sysdeps/unix/sysv/linux/_exit.c:
> 27
> #1 0x00007fdac9c825ae in gdk_event_source_check
> (base=base@entry=0x5626b0eb7770) at ../gtk/gdk/wayland/gdkeventsource.c:97
> #2 0x00007fdac962411f in g_main_context_check (context=0x5626b71d9be0,
> max_priority=2147483647, fds=<optimized out>, n_fds=<optimized out>) at ../
> glib/glib/gmain.c:4035
> #3 0x00007fdac9679e5e in g_main_context_iterate.constprop.0
> (context=context@entry=0x5626b71d9be0, block=block@entry=0,
> dispatch=dispatch@entry=0, self=<optimized out>) at ../glib/glib/gmain.c:4208
> #4 0x00007fdac962132d in g_main_context_pending (context=0x5626b71d9be0) at
> ../glib/glib/gmain.c:4241
> #5 0x00005626ab4f3bd2 in pgtk_read_socket.lto_priv ()
That's what I thought might be happening. Emacs calls
g_main_context_pending to read events from GDK, which notices that the
display connection has been abruptly terminated, and calls _exit to
abort.
Unfortunately, there's no way for us to fix this inside Emacs, so I
guess you should look into why Wayland display connections are so
unstable on your system.
next prev parent reply other threads:[~2022-08-05 0:50 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 7:36 bug#56967: 29.0.50; Frequent crashes under Wayland Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-04 8:01 ` Eli Zaretskii
[not found] ` <3230275.qDoO4GC8Cx@odin>
2022-08-04 8:21 ` Eli Zaretskii
2022-08-04 11:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 0:18 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 0:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-08-05 6:25 ` Eli Zaretskii
2022-08-05 6:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 6:43 ` Eli Zaretskii
2022-08-05 6:53 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 7:46 ` Eli Zaretskii
2022-08-05 8:26 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 8:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 6:56 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 6:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 11:40 ` Gregory Heytings
2022-08-05 11:50 ` Eli Zaretskii
[not found] ` <2972937.jrzt3BHeHG@odin>
2022-08-05 6:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-07 14:51 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-07 15:07 ` Eli Zaretskii
2022-08-07 15:14 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-07 15:44 ` Eli Zaretskii
2022-08-08 2:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-08 2:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-08 6:07 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-08 8:56 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-08 10:10 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-13 12:10 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-13 12:10 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-13 13:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-13 17:06 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 6:31 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <2189728.upBv5HjrgE@odin>
2022-08-05 6:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <1917872.q2Y8mqo1ke@odin>
2022-08-05 6:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 6:55 ` Bjoern Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 7:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-17 16:02 ` Gavin Massingham
[not found] <CAH3b6=SPM_Pys81fi-_Eu=VXO8mETqV+s0YFC+8c1huv4dmh9Q@mail.gmail.com>
2022-08-04 18:29 ` Eli Zaretskii
2022-08-05 7:34 ` Po Lu 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=878ro37bts.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=56967@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.de \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
/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).