bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#19282: 24.3; Emacs crashes as g_main_context_prepare() is called rec


From: Robert Pluim
Subject: bug#19282: 24.3; Emacs crashes as g_main_context_prepare() is called recursively
Date: Wed, 06 Jun 2018 10:00:14 +0200

Noam Postavsky <address@hidden> writes:

>> No symbol table info available.
>> #20 0x00007ffff4e9054b in _XError () from
>> /usr/lib/x86_64-linux-gnu/libX11.so.6
>> No symbol table info available.
>> #21 0x00007ffff4e8d5e7 in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
>> No symbol table info available.
>> #22 0x00007ffff4e8d695 in ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
>> No symbol table info available.
>> #23 0x00007ffff4e8dfc5 in _XEventsQueued () from
>> /usr/lib/x86_64-linux-gnu/libX11.so.6
>> No symbol table info available.
>> #24 0x00007ffff4e8012d in XPending () from
>> /usr/lib/x86_64-linux-gnu/libX11.so.6
>> No symbol table info available.
>> #25 0x00007ffff663dc1b in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
>> No symbol table info available.
>> #26 0x00007ffff55f368d in g_main_context_prepare () from
>> /lib/x86_64-linux-gnu/libglib-2.0.so.0
>> No symbol table info available.
>> #27 0x00007ffff55f3f03 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
>> No symbol table info available.
>> #28 0x00007ffff55f4097 in g_main_context_pending () from
>> /lib/x86_64-linux-gnu/libglib-2.0.so.0
>> No symbol table info available.
>> #29 0x00007ffff6a43d8d in gtk_events_pending () from
>> /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
>
> There's not enough info to go on here.  Can you build a newer version
> with debug symbols?  Some of it looks like it could be #31547, though
> behind all those "??" could easily be hiding something completely
> different.
>

XFT_DEBUG=16 emacs

(or even better 'XFT_DEBUG=16 emacs -xrm "emacs.synchronous: true"' to
run X synchronously)

might tell us what font emacs was trying to load. If itʼs some kind of
emoji font then itʼs Bug#31547, fixed on both master and emacs-26

Robert





reply via email to

[Prev in Thread] Current Thread [Next in Thread]