From: Andreas Schwab <schwab@linux-m68k.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25172@debbugs.gnu.org, "Elias Mårtenson" <lokedhs@gmail.com>,
clement.pit@gmail.com
Subject: bug#25172: 26.0.50; Concurrency feature, sit-for doesn't work (crashing and unexpected behaviour)
Date: Tue, 13 Dec 2016 19:25:19 +0100 [thread overview]
Message-ID: <87d1gv1yb4.fsf@linux-m68k.org> (raw)
In-Reply-To: <83h967bxwt.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 13 Dec 2016 18:23:46 +0200")
On Dez 13 2016, Eli Zaretskii <eliz@gnu.org> wrote:
> There's something here I don't understand. It looks like 9 threads
> are stuck in acquire_global_lock, which is fine. The main thread was
> executing some timer (probably, the one set up by global-eldoc-mode),
> when it was delivered SIGSEGV. There's one more thread running this:
>
> Stack trace of thread 23775:
> #0 0x00007f5687e5e426 __sigsuspend (libc.so.6)
> #1 0x0000000000578385 deliver_thread_signal (emacs-26.0.50)
> #2 0x00000000005783f8 deliver_fatal_thread_signal (emacs-26.0.50)
> #3 0x00000000005785ae handle_sigsegv (emacs-26.0.50)
> #4 0x00007f5688810080 n/a (libpthread.so.0)
>
> This seems to be some thread, which was hit by SIGSEGV, and since it
> is not the main thread, it calls pdthread_kill to kill the main
> thread, which explains why the main thread received the signal. But
> what I don't understand is what was this thread 23775 doing before it
> hit SIGSEGV? The backtrace stops at handle_sigsegv, without revealing
> that.
Installing debuginfo for glibc and/or `thread apply all bt' will most
likely give more information.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2016-12-13 18:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-11 16:35 bug#25172: 26.0.50; Concurrency feature, sit-for doesn't work (crashing and unexpected behaviour) Elias Mårtenson
2016-12-11 16:47 ` Andreas Schwab
2016-12-11 16:49 ` Elias Mårtenson
2016-12-11 17:54 ` Eli Zaretskii
2016-12-11 17:52 ` Eli Zaretskii
2016-12-11 19:05 ` Clément Pit--Claudel
2016-12-12 4:50 ` Elias Mårtenson
2016-12-12 17:37 ` Eli Zaretskii
2016-12-13 2:38 ` Elias Mårtenson
2016-12-13 3:40 ` Eli Zaretskii
2016-12-13 3:45 ` Elias Mårtenson
2016-12-13 4:11 ` Elias Mårtenson
2016-12-13 4:14 ` Elias Mårtenson
2016-12-13 4:16 ` Elias Mårtenson
2016-12-13 16:26 ` Eli Zaretskii
2016-12-14 2:58 ` Elias Mårtenson
2016-12-14 3:00 ` Elias Mårtenson
2016-12-14 3:02 ` Elias Mårtenson
2016-12-14 16:03 ` Eli Zaretskii
2016-12-14 16:12 ` Elias Mårtenson
2016-12-15 3:30 ` Elias Mårtenson
2016-12-15 16:22 ` Eli Zaretskii
2016-12-15 16:28 ` Elias Mårtenson
2016-12-15 16:59 ` Eli Zaretskii
2016-12-13 16:23 ` Eli Zaretskii
2016-12-13 18:25 ` Andreas Schwab [this message]
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=87d1gv1yb4.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=25172@debbugs.gnu.org \
--cc=clement.pit@gmail.com \
--cc=eliz@gnu.org \
--cc=lokedhs@gmail.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 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.