Subject: Re: bug#36902: Emacs crashed under X11 suddenly

From: leo <[email-masked]>
Date: Thu, 08 Aug 2019 09:30:24 +1000

Hi Eli

Thanks fro the manual info about `addr2line`. I have converted the 
addresses of the crash report:

```
emacs_backtrace
??:0
terminate_due_to_signal
/home/wolly/installs/emacs-26.1/src/emacs.c:378
emacs_abort
??:0
redisplay_internal
/home/wolly/installs/emacs-26.1/src/xdisp.c:13827
redisplay_preserve_echo_area
/home/wolly/installs/emacs-26.1/src/xdisp.c:14631
Fdelete_process
??:0
kill_buffer_processes
??:0
shut_down_emacs
/home/wolly/installs/emacs-26.1/src/emacs.c:2097
x_connection_closed
xterm.c:0
x_io_error_quitter
xterm.c:0
??
??:0
??
??:0
??
??:0
??
??:0
??
??:0
??
??:0
??
??:0
??
??:0
XTread_socket
xterm.c:0
gobble_input
/home/wolly/installs/emacs-26.1/src/keyboard.c:6909
process_pending_signals
/home/wolly/installs/emacs-26.1/src/keyboard.c:7150
wait_reading_process_output
??:0
kbd_buffer_get_event
/home/wolly/installs/emacs-26.1/src/keyboard.c:3831
read_event_from_main_queue
/home/wolly/installs/emacs-26.1/src/keyboard.c:2151
read_decoded_event_from_main_queue
/home/wolly/installs/emacs-26.1/src/keyboard.c:2214
read_char
/home/wolly/installs/emacs-26.1/src/keyboard.c:2802
read_key_sequence.constprop.36
/home/wolly/installs/emacs-26.1/src/keyboard.c:9147
command_loop_1
/home/wolly/installs/emacs-26.1/src/keyboard.c:1368
internal_condition_case
??:0
command_loop_2
/home/wolly/installs/emacs-26.1/src/keyboard.c:1111
internal_catch
??:0
command_loop
/home/wolly/installs/emacs-26.1/src/keyboard.c:1093
recursive_edit_1
/home/wolly/installs/emacs-26.1/src/keyboard.c:696
SPECPDL_INDEX
/home/wolly/installs/emacs-26.1/src/lisp.h:3130
Frecursive_edit
/home/wolly/installs/emacs-26.1/src/keyboard.c:738
main
/home/wolly/installs/emacs-26.1/src/emacs.c:1716
??
??:0
_start
??:0
```

HTH,
Leo

&nbsp;

On 3 Aug 2019, at 17:03, Eli Zaretskii wrote:

>> From: leo <[email-masked]>
>> Date: Sat, 03 Aug 2019 16:34:24 +1000
>>
>> Emacs crashed under X11 suddenly. Emacs was idle for a few minutes. 
>> This
>> has append before, but does not happen all the time.
>>
>> Emacs was running under RHEL 6 and displayed via the X server 
>> MobaXterm
>> on Windows 7.
>>
>> Emacs outputted the following on the console it was started from:
>>
>> Fatal error 6: Aborted
>> Backtrace:
>> emacs[0x504ba2]
>> emacs[0x4ea224]
>> emacs[0x504c33]
>> emacs[0x450752]
>> emacs[0x452ddd]
>> emacs[0x599f24]
>> emacs[0x5a16b5]
>> emacs[0x4ea044]
>> emacs[0x4b9ff2]
>> emacs[0x4ba126]
>> /usr/lib64/libX11.so.6(_XIOError+0x4e)[0x38d804488e]
>> /usr/lib64/libX11.so.6(_XEventsQueued+0x7d)[0x38d80436ed]
>> /usr/lib64/libX11.so.6(XPending+0x5d)[0x38d803437d]
>> /usr/lib64/libgdk-x11-2.0.so.0[0x38dac60492]
>> /lib64/libglib-2.0.so.0(g_main_context_prepare+0x1a6)[0x38d6044496]
>> /lib64/libglib-2.0.so.0[0x38d60448e1]
>> /lib64/libglib-2.0.so.0(g_main_context_pending+0x64)[0x38d6044fd4]
>> /usr/lib64/libgtk-x11-2.0.so.0(gtk_events_pending+0x19)[0x38dd54dc19]
>
> Please use the technique described in the Emacs manual's node
> "Crashing" to convert these addresses into a human-readable list of
> files, function names, and line numbers.
>
> Thanks.