From: Eli Zaretskii <eliz@gnu.org>
To: Aaron Jensen <aaronjensen@gmail.com>
Cc: 30364@debbugs.gnu.org, alan@idiocy.org, eggert@cs.ucla.edu,
npostavs@users.sourceforge.net, npostavs@gmail.com,
schwab@linux-m68k.org
Subject: bug#30364: 26.0.91; thread crash on macos
Date: Wed, 28 Feb 2018 19:38:43 +0200 [thread overview]
Message-ID: <83371lypy4.fsf@gnu.org> (raw)
In-Reply-To: <CAHyO48y2sGrVaQUCts=LzK1uA_GoGt+sxkK6Su_YOg+Zp5CTFg@mail.gmail.com> (message from Aaron Jensen on Wed, 28 Feb 2018 09:32:08 -0800)
> From: Aaron Jensen <aaronjensen@gmail.com>
> Date: Wed, 28 Feb 2018 09:32:08 -0800
> Cc: Paul Eggert <eggert@cs.ucla.edu>, Andreas Schwab <schwab@linux-m68k.org>,
> Noam Postavsky <npostavs@gmail.com>, 30364@debbugs.gnu.org,
> Noam Postavsky <npostavs@users.sourceforge.net>, Alan Third <alan@idiocy.org>
>
> No. I'm sorry I've apparently done such a terrible job of explaining
> this. I ran into this when using a single thread. You only need one
> thread that triggers a GC to cause this, it just needs to happen to
> happen during that thread.
But that is a macOS only problem, because the default stack size is
ridiculously small. The fix that got installed, OTOH, is much more
general.
If you want to make a macOS-only change that enlarges its stack we
give to threads, I can live with that on emacs-26, provided that the
fix only affects threads other than the main one.
Thanks.
next prev parent reply other threads:[~2018-02-28 17:38 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 8:21 bug#30364: 26.0.91; thread crash on macos Aaron Jensen
2018-02-14 1:05 ` Noam Postavsky
2018-02-14 1:22 ` Aaron Jensen
2018-02-17 14:44 ` Noam Postavsky
2018-02-17 17:58 ` Aaron Jensen
2018-02-17 18:17 ` Eli Zaretskii
2018-02-17 18:40 ` Aaron Jensen
2018-02-17 18:55 ` Eli Zaretskii
2018-02-18 1:58 ` Aaron Jensen
2018-02-18 4:51 ` Eli Zaretskii
2018-02-18 4:54 ` Aaron Jensen
2018-02-18 16:45 ` Eli Zaretskii
[not found] ` <CAHyO48y+c21biWxQDTMvW2PkSKW6TzZVWQ94yUPN_4n3utDv5A@mail.gmail.com>
2018-02-18 18:25 ` Eli Zaretskii
2018-02-18 18:38 ` Aaron Jensen
2018-02-18 18:39 ` Aaron Jensen
2018-02-18 18:59 ` Aaron Jensen
2018-02-18 19:32 ` Eli Zaretskii
2018-02-18 19:49 ` Aaron Jensen
2018-02-18 20:15 ` Eli Zaretskii
2018-02-18 21:12 ` Aaron Jensen
2018-02-19 3:29 ` Eli Zaretskii
2018-02-19 17:24 ` Paul Eggert
2018-02-19 17:29 ` Daniel Colascione
2018-02-19 18:39 ` Eli Zaretskii
2018-02-19 18:33 ` Eli Zaretskii
2018-02-19 18:47 ` Aaron Jensen
2018-02-19 20:08 ` Paul Eggert
2018-02-19 20:16 ` Aaron Jensen
2018-02-25 20:52 ` Aaron Jensen
2018-02-27 17:30 ` Paul Eggert
2018-02-27 17:38 ` Aaron Jensen
2018-02-27 17:44 ` Paul Eggert
2018-02-28 5:33 ` Aaron Jensen
2018-02-28 15:33 ` Eli Zaretskii
2018-02-28 15:35 ` Aaron Jensen
2018-02-28 16:20 ` Eli Zaretskii
2018-02-28 17:32 ` Aaron Jensen
2018-02-28 17:38 ` Eli Zaretskii [this message]
2018-02-28 17:59 ` Aaron Jensen
2018-02-28 18:07 ` Aaron Jensen
2018-02-28 19:15 ` Paul Eggert
2018-02-28 20:36 ` Eli Zaretskii
2018-03-01 0:31 ` Paul Eggert
2018-03-01 8:37 ` Aaron Jensen
2018-05-13 15:13 ` Noam Postavsky
2018-05-13 16:26 ` Eli Zaretskii
2018-05-14 20:03 ` Paul Eggert
2018-02-28 16:19 ` Paul Eggert
2018-02-18 19:07 ` Eli Zaretskii
2018-02-18 19:04 ` Eli Zaretskii
2018-02-18 11:01 ` Alan Third
2018-02-17 18:23 ` Alan Third
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=83371lypy4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30364@debbugs.gnu.org \
--cc=aaronjensen@gmail.com \
--cc=alan@idiocy.org \
--cc=eggert@cs.ucla.edu \
--cc=npostavs@gmail.com \
--cc=npostavs@users.sourceforge.net \
--cc=schwab@linux-m68k.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.