From: Eli Zaretskii <eliz@gnu.org>
To: leo <devel@halloleo.hailmail.net>
Cc: 36902@debbugs.gnu.org
Subject: bug#36902: Emacs crashed under X11 suddenly
Date: Sat, 03 Aug 2019 10:03:05 +0300 [thread overview]
Message-ID: <83wofueno6.fsf@gnu.org> (raw)
In-Reply-To: <B7312636-64D2-4D0A-AA1A-5F78FE588B38@halloleo.hailmail.net> (message from leo on Sat, 03 Aug 2019 16:34:24 +1000)
> From: leo <devel@halloleo.hailmail.net>
> 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.
next prev parent reply other threads:[~2019-08-03 7:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-03 6:34 bug#36902: Emacs crashed under X11 suddenly leo
2019-08-03 7:03 ` Eli Zaretskii [this message]
2019-08-07 23:30 ` leo
2019-08-10 9:00 ` Eli Zaretskii
2019-08-11 9:35 ` leo
2019-08-11 14:18 ` Eli Zaretskii
2019-08-21 15:42 ` Stefan Kangas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wofueno6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36902@debbugs.gnu.org \
--cc=devel@halloleo.hailmail.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.