unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Bruce Adams <bruce@optibrium.com>
Cc: 65811@debbugs.gnu.org, kbrown@cornell.edu
Subject: bug#65811: 27.1; zzzzzzzz forever
Date: Fri, 08 Sep 2023 18:30:35 +0300	[thread overview]
Message-ID: <83ledgwulg.fsf@gnu.org> (raw)
In-Reply-To: <DBAPR05MB71732C43250FB62FB16B6984B5EDA@DBAPR05MB7173.eurprd05.prod.outlook.com> (message from Bruce Adams on Fri, 8 Sep 2023 15:10:06 +0000)

> From: Bruce Adams <bruce@optibrium.com>
> CC: "65811@debbugs.gnu.org" <65811@debbugs.gnu.org>
> Date: Fri, 8 Sep 2023 15:10:06 +0000
> 
> I have a backtrace here:
> 
> apt-get changelog emacs
> Get:1 https://changelogs.ubuntu.com emacs 1:27.1+1-3ubuntu5.1 Changelog [113 kB]
> Fetched 113 kB in 1s (157 kB/s)
> brucea@Bruce-PC-23:~/work/git/ubuntu-servers$ Connection lost to X server ':0'
> When compiled with GTK, Emacs cannot recover from X disconnects.
> This is a GTK bug: https://gitlab.gnome.org/GNOME/gtk/issues/221
> For details, see etc/PROBLEMS.
> Backtrace:
> emacs(+0x150e55)[0x55b8db8bde55]
> emacs(+0x4aa38)[0x55b8db7b7a38]
> emacs(+0x4af4f)[0x55b8db7b7f4f]
> emacs(+0x49f22)[0x55b8db7b6f22]
> emacs(+0x49ff3)[0x55b8db7b6ff3]
> /lib/x86_64-linux-gnu/libX11.so.6(_XIOError+0x63)[0x7f076d2c82f3]
> /lib/x86_64-linux-gnu/libX11.so.6(_XReply+0x3ef)[0x7f076d2cd56f]
> /lib/x86_64-linux-gnu/libX11.so.6(XGetWindowProperty+0x108)[0x7f076d2ac568]
> /lib/x86_64-linux-gnu/libgdk-3.so.0(+0x781f9)[0x7f076da6a1f9]
> /lib/x86_64-linux-gnu/libgdk-3.so.0(+0x7830e)[0x7f076da6a30e]
> /lib/x86_64-linux-gnu/libgdk-3.so.0(gdk_x11_screen_supports_net_wm_hint+0x8c)[0x7f076da6b4dc]
> /lib/x86_64-linux-gnu/libgdk-3.so.0(+0x7fb4f)[0x7f076da71b4f]
> /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0x1290)[0x7f076d55b700]
> /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x93)[0x7f076d55b863]
> /lib/x86_64-linux-gnu/libgdk-3.so.0(+0x46966)[0x7f076da38966]
> /lib/x86_64-linux-gnu/libgdk-3.so.0(+0x332ad)[0x7f076da252ad]
> /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x562c8)[0x7f076d4452c8]
> /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x174)[0x7f076d444c44]
> /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0xab258)[0x7f076d49a258]
> /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x33)[0x7f076d4423e3]
> /lib/x86_64-linux-gnu/libgtk-3.so.0(gtk_main_iteration+0x19)[0x7f076dd43d99]
> emacs(+0x104fd3)[0x55b8db871fd3]
> emacs(+0x13d3e2)[0x55b8db8aa3e2]
> emacs(+0x13d9d5)[0x55b8db8aa9d5]
> emacs(+0x1f8c95)[0x55b8db965c95]
> emacs(+0x14158f)[0x55b8db8ae58f]
> emacs(+0x143b6a)[0x55b8db8b0b6a]
> emacs(+0x14530c)[0x55b8db8b230c]
> emacs(+0x1b2f67)[0x55b8db91ff67]
> emacs(+0x1360f0)[0x55b8db8a30f0]
> emacs(+0x1b2ea9)[0x55b8db91fea9]
> emacs(+0x13607e)[0x55b8db8a307e]
> emacs(+0x13b68a)[0x55b8db8a868a]
> emacs(+0x13b9c9)[0x55b8db8a89c9]
> emacs(+0x52aca)[0x55b8db7bfaca]
> /lib/x86_64-linux-gnu/libc.so.6(+0x29d90)[0x7f076bc56d90]
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80)[0x7f076bc56e40]
> emacs(+0x531b5)[0x55b8db7c01b5]
> 
> [1]+  Aborted                 emacs

Thanks, but those addresses can only be interpreted on your machine.
So either use the method described in the node "Crashing" of the Emacs
user manual, or (better) run Emacs under GDB, and when it crashes and
GDB gets control, type at the GDB prompt:

  (gdb) thread apply all bt

and post here everything that GDB shows in response.





  reply	other threads:[~2023-09-08 15:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-07 20:33 bug#65811: 27.1; zzzzzzzz forever Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-08  3:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-08  7:39   ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-08  7:56   ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-08 11:49     ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-08 13:14       ` Eli Zaretskii
2023-09-08 15:02         ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-09  1:01           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-08 15:10         ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-08 15:30           ` Eli Zaretskii [this message]
2023-09-08 19:54             ` Bruce Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-09  1:00           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-08 12:37   ` Eli Zaretskii
2023-09-08  5:47 ` Eli Zaretskii

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=83ledgwulg.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=65811@debbugs.gnu.org \
    --cc=bruce@optibrium.com \
    --cc=kbrown@cornell.edu \
    /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).