From: Eli Zaretskii <eliz@gnu.org>
To: Elias Martenson <elias.martenson@murex.com>
Cc: 25178@debbugs.gnu.org
Subject: bug#25178: 26.0.50; Crash when pressing C-g in TTY mode
Date: Tue, 13 Dec 2016 20:45:25 +0200 [thread overview]
Message-ID: <838trjbrcq.fsf@gnu.org> (raw)
In-Reply-To: <yxd8wpf4msrn.fsf@murex.com> (message from Elias Martenson on Tue, 13 Dec 2016 11:07:08 +0800)
> From: Elias Martenson <elias.martenson@murex.com>
> CC: <25178@debbugs.gnu.org>
> Date: Tue, 13 Dec 2016 11:07:08 +0800
>
> Here is the actual stack trace from the core dump generated during the
> crash:
>
> Machine ID: 50467f3a69eb4dbea19c8a2972949839
> Hostname: em-desktop
> Storage: /var/lib/systemd/coredump/core.emacs.50067.45a62f2ad9804a0b81fed25ad8faffab.21460.1481598260000000000000.lz4
> Message: Process 21460 (emacs) of user 50067 dumped core.
>
> Stack trace of thread 21460:
> #0 0x00007fec16127f5f raise (libpthread.so.0)
> #1 0x0000000000553c66 terminate_due_to_signal (emacs-26.0.50)
> #2 0x00000000005783c1 handle_fatal_signal (emacs-26.0.50)
> #3 0x0000000000578392 deliver_thread_signal (emacs-26.0.50)
> #4 0x00000000005783f8 deliver_fatal_thread_signal (emacs-26.0.50)
> #5 0x00000000005785ae handle_sigsegv (emacs-26.0.50)
> #6 0x00007fec16128080 __restore_rt (libpthread.so.0)
> #7 0x00007fec161296a0 __lll_unlock_elision (libpthread.so.0)
> #8 0x0000000000677a94 sys_mutex_unlock (emacs-26.0.50)
> #9 0x000000000067638d release_global_lock (emacs-26.0.50)
> #10 0x0000000000676d75 really_call_select (emacs-26.0.50)
> #11 0x00000000005d4a02 flush_stack_call_func (emacs-26.0.50)
> #12 0x0000000000676e2b thread_select (emacs-26.0.50)
> #13 0x0000000000651168 wait_reading_process_output (emacs-26.0.50)
> #14 0x00000000004252be sit_for (emacs-26.0.50)
> #15 0x000000000055bc48 read_char (emacs-26.0.50)
Hmm... Is calling pthread_mutex_unlock twice in a row, without an
intervening call to pthread_mutex_lock, supposed to segfault? Posix
seems to say the result is undefined behavior, but AFAICT by looking
in the glibc sources, its implementation triggers a crash in that
case.
Strangely, I don't see this on the GNU/Linux system to which I have
access, although Emacs definitely calls pthread_mutex_unlock twice in
a row in the scenario of this bug report. Is this some change in
latest versions of glibc?
next prev parent reply other threads:[~2016-12-13 18:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 4:33 bug#25178: 26.0.50; Crash when pressing C-g in TTY mode Elias Martenson
2016-12-12 16:56 ` Eli Zaretskii
2016-12-13 2:52 ` Elias Martenson
2016-12-13 3:07 ` Elias Martenson
2016-12-13 18:45 ` Eli Zaretskii [this message]
2016-12-13 19:26 ` Andreas Schwab
2016-12-13 19:37 ` Eli Zaretskii
2016-12-13 20:12 ` Andreas Schwab
2016-12-14 3:13 ` Elias Martenson
2016-12-14 3:09 ` Elias Martenson
2016-12-14 3:39 ` Eli Zaretskii
2016-12-14 5:41 ` Elias Martenson
2016-12-17 13:58 ` Eli Zaretskii
2016-12-19 2:48 ` Elias Martenson
[not found] ` <E1cJ1Z7-0000yc-Dd@eggs.gnu.org>
2017-01-05 23:39 ` npostavs
2017-01-06 7:47 ` Eli Zaretskii
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=838trjbrcq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25178@debbugs.gnu.org \
--cc=elias.martenson@murex.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.