From: raman <raman@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25164@debbugs.gnu.org
Subject: bug#25164: 26.0.50; Concurrency: (make-thread #'gnus "gnus") Crashes Emacs
Date: Sun, 11 Dec 2016 13:31:40 -0800 [thread overview]
Message-ID: <p91fulu40g3.fsf@google.com> (raw)
In-Reply-To: <83lgvme926.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 11 Dec 2016 18:15:29 +0200")
This log may give you some more info.
I placed the expression
(make-thread #'gnus "gnus")
in a file "g.el" , then started emacs like so:
emacs -l g.el & from an XTErm.
That started successfuly and even started gnus.
Then I evaluated the same expression in the minibuffer and that emacs
aborted.
i then grabbed the log output to that XTerm -- here's what it says:
In case it matters, I'm using stumpwm as my window manager, not gnome.
13:27:17 raman-glaptop2 tmp $ [xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been ca
lled
[xcb] Aborting, sorry about that.
emacs: ../../src/xcb_io.c:274: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Backtrace:
emacs[0x505758]
emacs[0x505849]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10330)[0x7ffff1300330]
/lib/x86_64-linux-gnu/libc.so.6(gsi
gnal+0x37)[0x7ffff0b59c37]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7ffff0b5d028]
/lib/x86_64-linux-gnu/libc.so.6(+0x2fbf6)[0x7ffff0b52bf6]
/lib/x86_64-linux-gnu/libc.so.6(+0x2fca2)[0x7ffff0b52ca2]
/usr/lib/x86_64-linux-gnu/libX11.so.6(+0x3bc69)[0x7ffff51b7c69]
/usr/lib/x
86_64-linux-gnu/libX11.so.6(+0x3bcfc)[0x7ffff51b7cfc]
/usr/lib/x86_64-linux-gnu/libX11.so.6(_XEventsQueued+0x5d)[0x7ffff51b7fcd]
/usr/lib/x86_64-linux-gnu/libX11.so.6(XPending+0x4d)[0x7ffff51aa12d]
/usr/lib/x86_64-linux-gnu/libgdk-3.so.0(+0x4cceb)[0x7ffff6966ceb]
/lib/x86_64-l
inux-gnu/libglib-2.0.so.0(g_main_context_prepare+0x15d)[0x7ffff591d68d]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x48f03)[0x7ffff591df03]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_pending+0x27)[0x7ffff591e097]
emacs[0x5dd798]
emacs[0x5c08b3]
emacs[0x5497dc]
emacs[0x5c
1047]
emacs[0x5a5840]
emacs[0x4f84f7]
emacs[0x580b8a]
emacs[0x562a3e]
emacs[0x59a7dd]
emacs[0x5629b3]
emacs[0x5c0d73]
emacs[0x560f5d]
emacs[0x5c0c77]
/
lib/x86_64-linux-gnu/libpthread.so.0(+0x8184)[0x7ffff12f8184]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7ffff0c1d37d]
...
--
next prev parent reply other threads:[~2016-12-11 21:31 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-12-11 4:00 bug#25164: 26.0.50; Concurrency: (make-thread #'gnus "gnus") Crashes Emacs raman 2016-12-11 16:15 ` Eli Zaretskii 2016-12-11 16:46 ` raman 2016-12-11 17:40 ` Eli Zaretskii 2016-12-11 20:16 ` raman 2016-12-11 20:41 ` Eli Zaretskii 2016-12-11 21:31 ` raman [this message] 2017-01-14 4:35 ` npostavs
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=p91fulu40g3.fsf@google.com \
--to=raman@google.com \
--cc=25164@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).