From: "Elias Mårtenson" <lokedhs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25172@debbugs.gnu.org, "Clément Pit--Claudel" <clement.pit@gmail.com>
Subject: bug#25172: 26.0.50; Concurrency feature, sit-for doesn't work (crashing and unexpected behaviour)
Date: Wed, 14 Dec 2016 10:58:36 +0800 [thread overview]
Message-ID: <CADtN0WKnu_ZeSRXwyGyq-KR=8CxdPe_J+fDjCmGyo5_e43O+6Q@mail.gmail.com> (raw)
In-Reply-To: <83fulrbxsd.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]
On 14 December 2016 at 00:26, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Elias Mårtenson <lokedhs@gmail.com>
> > Date: Tue, 13 Dec 2016 12:16:41 +0800
> > Cc: Clément Pit--Claudel <clement.pit@gmail.com>,
> > 25172@debbugs.gnu.org
> >
> > This is the output from the SIGABRT case. Again, there is a lot of
> information before the actual "bt full" output:
>
> This shows exactly the situation which I imagined could happen: 3
> threads, including the main thread, all running the code in xg_select
> which calls unblock_input, and aborting due to the block level being
> negative.
>
> Can you try removing the calls to block_input/unblock_input from
> xgselect.c, and see if these crashes then stop?
>
I have tried this now, and it's much more stable now. It doesn't
immediately crash, and sometimes it doesn't crash at all.
When it crashes, it does so after several seconds, and I have captured two
of these crashes.
I will post these backtraces in the following two emails.
Regards,
Elias
[-- Attachment #2: Type: text/html, Size: 1657 bytes --]
next prev parent reply other threads:[~2016-12-14 2:58 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 [this message]
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
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='CADtN0WKnu_ZeSRXwyGyq-KR=8CxdPe_J+fDjCmGyo5_e43O+6Q@mail.gmail.com' \
--to=lokedhs@gmail.com \
--cc=25172@debbugs.gnu.org \
--cc=clement.pit@gmail.com \
--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 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.