From: Eli Zaretskii <eliz@gnu.org>
To: Alex <agrambot@gmail.com>
Cc: 28630@debbugs.gnu.org, tom@tromey.com
Subject: bug#28630: 27.0.50; C-g while a non-main thread is sitting crashes Emacs
Date: Sun, 01 Oct 2017 21:32:22 +0300 [thread overview]
Message-ID: <83o9pq3eix.fsf@gnu.org> (raw)
In-Reply-To: <87d166rb6n.fsf@gmail.com> (message from Alex on Sun, 01 Oct 2017 12:10:40 -0600)
> From: Alex <agrambot@gmail.com>
> Cc: 28630@debbugs.gnu.org, tom@tromey.com
> Date: Sun, 01 Oct 2017 12:10:40 -0600
>
> >> Should this be labelled a blocker for Emacs 26?
> >
> > Maybe I'm not sure. It doesn't sound like threads are used much, if
> > at all, which would make blocking on it silly.
>
> It's understandable that bug 25214 isn't a blocker for this reason, but
> I think crashing is severe enough to be a blocker, especially since it's
> somewhat trivial to trigger.
If this trigger never happens in real life, why should we block on it?
More generally, if no one besides my sorry self is interested in using
this feature, let alone fixing its bugs, maybe we should simply remove
it from Emacs.
> > Is your Emacs built with --enable-checking? Because I get an
> > assertion violation in that case, not a crash.
>
> I just tried building with "./configure --enable-checking" and it still
> crashes for me.
Strange, that's not what I see.
I hope to have some time soon to look into this. I think I understand
the root cause: we are longjmp-ing in a thread other than the one
which called setjmp.
next prev parent reply other threads:[~2017-10-01 18:32 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 7:22 bug#28630: 27.0.50; C-g while a non-main thread is sitting crashes Emacs Alex
2017-10-01 3:18 ` Alex
2017-10-01 15:01 ` Eli Zaretskii
2017-10-01 18:10 ` Alex
2017-10-01 18:32 ` Eli Zaretskii [this message]
2017-10-02 4:30 ` YAMAMOTO Mitsuharu
2017-10-02 12:43 ` YAMAMOTO Mitsuharu
2017-10-02 16:08 ` Eli Zaretskii
2017-10-04 7:39 ` Eli Zaretskii
2017-10-04 7:49 ` YAMAMOTO Mitsuharu
2017-10-04 8:16 ` Eli Zaretskii
2017-10-04 8:32 ` YAMAMOTO Mitsuharu
2017-10-04 9:23 ` Eli Zaretskii
2017-10-05 3:27 ` YAMAMOTO Mitsuharu
2017-10-05 7:24 ` Eli Zaretskii
2017-10-07 13:53 ` Philipp Stephani
2017-10-07 14:24 ` Eli Zaretskii
2017-10-07 14:50 ` Eli Zaretskii
2017-10-09 8:21 ` YAMAMOTO Mitsuharu
2017-10-09 8:38 ` Eli Zaretskii
2017-10-09 10:34 ` mituharu
2017-10-09 11:01 ` Eli Zaretskii
2017-10-04 7:39 ` YAMAMOTO Mitsuharu
2017-10-04 8:14 ` Eli Zaretskii
2017-10-02 5:11 ` Eric Abrahamsen
2017-10-02 15:54 ` Eli Zaretskii
2017-10-03 9:35 ` Dmitry Gutov
2017-10-03 14:38 ` Eli Zaretskii
2017-10-03 14:50 ` Philipp Stephani
2017-10-03 15:45 ` Eli Zaretskii
2017-10-03 16:22 ` Philipp Stephani
2017-10-03 16:35 ` Eli Zaretskii
2017-10-03 17:04 ` Philipp Stephani
2017-10-01 10:08 ` Alan Third
2017-10-01 15:03 ` 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=83o9pq3eix.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28630@debbugs.gnu.org \
--cc=agrambot@gmail.com \
--cc=tom@tromey.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.