From: Eli Zaretskii <eliz@gnu.org>
To: Jan Synacek <jsynacek@redhat.com>
Cc: 30874@debbugs.gnu.org
Subject: bug#30874: 27.0.50; Emacs crashes
Date: Thu, 22 Mar 2018 16:55:09 +0200 [thread overview]
Message-ID: <83vadoi2ia.fsf@gnu.org> (raw)
In-Reply-To: <CAPsXM8WJDeX+US110XtB=fP8noBQaNO8QE0KpYZn2GPViOs3SA@mail.gmail.com> (message from Jan Synacek on Thu, 22 Mar 2018 14:05:26 +0100)
> From: Jan Synacek <jsynacek@redhat.com>
> Date: Thu, 22 Mar 2018 14:05:26 +0100
> Cc: 30874@debbugs.gnu.org
>
> > What about adding the -xrm "emacs.synchronous: true" switch to the
> > Emacs invocation command -- does it also not work?
>
> As far as I can tell, no. I still see the emacs frame remain open but
> unresponsive and also see the same backtrace as before.
Exactly the same backtrace? The backtrace you posted:
#19 0x00000000004c2fcb in x_error_handler (display=0x2c59000,
event=0x7fffffff5d40) at xterm.c:9889
#20 0x00007ffff469ce3a in _XError () at /lib64/libX11.so.6
#21 0x00007ffff4699d6b in handle_error () at /lib64/libX11.so.6
---Type <return> to continue, or q <return> to quit---
#22 0x00007ffff4699e15 in handle_response () at /lib64/libX11.so.6
#23 0x00007ffff469a745 in _XEventsQueued () at /lib64/libX11.so.6
#24 0x00007ffff468c2bd in XPending () at /lib64/libX11.so.6
#25 0x00007ffff64f2c2e in gdk_event_source_prepare () at /lib64/libgdk-3.so.0
#26 0x00007ffff4e033f9 in g_main_context_prepare () at /lib64/libglib-2.0.so.0
#27 0x00007ffff4e03dcb in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#28 0x00007ffff4e03f57 in g_main_context_pending () at /lib64/libglib-2.0.so.0
#29 0x00007ffff69b2d1d in gtk_events_pending () at /lib64/libgtk-3.so.0
#30 0x00000000004bfee7 in XTread_socket (terminal=<optimized out>,
hold_quit=0x7fffffff6040) at xterm.c:9146
#31 0x00000000004f7301 in gobble_input () at keyboard.c:6890
#32 0x00000000004f7925 in handle_async_input () at keyboard.c:7127
#33 0x00000000004f7925 in process_pending_signals () at keyboard.c:7141
#34 0x00000000005c8e5c in xftfont_open (f=0x13f0c30
<bss_sbrk_buffer+8312368>, entity=0x1243cb5 <bss_sbrk_buffer+6555317>,
pixel_size=15) at xftfont.c:391
indicates that the X error message was read when Emacs unblocked input
in xftfont_open, and read pending input. In synchronous X operation,
the call to x_error_handler should come from an X function, not from
process_pending_signals. I hoped that seeing the X function that
caused the error will allow us to understand better what is causing
the problem. If you still see exactly the same backtrace in
synchronous X operation, then I don't see any path forward, except
saying that telling Emacs Dejavu Sans Mono can cover the entire
Unicode range of characters is not recommended. (But when I did that
with a couple of fonts here, Emacs didn't crash.) It could be a
problem in the font backend you use, or it could be something else.
Thanks.
next prev parent reply other threads:[~2018-03-22 14:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 10:24 bug#30874: 27.0.50; Emacs crashes Jan Synacek
2018-03-20 12:04 ` Eli Zaretskii
2018-03-20 12:12 ` Jan Synacek
2018-03-20 12:44 ` Eli Zaretskii
2018-03-22 12:28 ` Jan Synacek
2018-03-22 13:01 ` Eli Zaretskii
2018-03-22 13:05 ` Jan Synacek
2018-03-22 14:55 ` Eli Zaretskii [this message]
2018-03-26 9:12 ` Jan Synacek
2018-03-26 10:33 ` Robert Pluim
2018-03-26 15:25 ` Eli Zaretskii
2018-03-26 16:52 ` Robert Pluim
2018-03-26 17:33 ` Eli Zaretskii
2018-03-26 20:17 ` Robert Pluim
2018-03-26 22:16 ` Robert Pluim
2018-03-27 3:02 ` Eli Zaretskii
2018-03-27 8:57 ` Robert Pluim
2018-03-29 10:25 ` Eli Zaretskii
2018-03-29 16:14 ` Robert Pluim
2018-03-29 17:07 ` Eli Zaretskii
2018-03-30 5:10 ` Glenn Morris
2018-03-30 8:00 ` Eli Zaretskii
2018-03-30 10:36 ` Robert Pluim
2018-03-30 11:46 ` Eli Zaretskii
2018-03-30 13:00 ` Robert Pluim
2018-03-30 13:46 ` Eli Zaretskii
2018-03-31 13:55 ` Robert Pluim
2018-03-31 14:59 ` Eli Zaretskii
2018-04-03 9:24 ` Robert Pluim
2018-04-03 8:00 ` Jan Synacek
2018-04-03 9:22 ` Robert Pluim
2018-04-03 9:42 ` Eli Zaretskii
2018-04-03 12:52 ` Robert Pluim
2018-03-29 10:35 ` Jan Synacek
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=83vadoi2ia.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30874@debbugs.gnu.org \
--cc=jsynacek@redhat.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).