From: Pip Cet <pipcet@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rpluim@gmail.com, 38748@debbugs.gnu.org, alan@idiocy.org,
andreyk.mad@gmail.com, jguenther@gmail.com
Subject: bug#38748: 28.0.50; crash on MacOS 10.15.2
Date: Wed, 8 Jan 2020 20:39:43 +0000 [thread overview]
Message-ID: <CAOqdjBc8kN-nb=4qf7hUd-9sPD0cae75j7SnKpN-K25pY=FVHQ@mail.gmail.com> (raw)
In-Reply-To: <8336cpbtzh.fsf@gnu.org>
On Wed, Jan 8, 2020 at 7:58 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > > Yes. Iʼll note that when this happens there are over 9000 stackframes,
> > > so perhaps itʼs stack exhaustion. macOS has a default stack of 8192
> > > kB, Iʼll see if increasing it helps.
> > That does sound like infinite recursion, or infinite recursion waiting
> > for something to change asynchronously that breaks the loop.
> No, GC is known to take many thousands of recursive calls to
> mark_object. 9000 is not a particularly high number, and doesn't
> necessarily signal infinite recursion.
In general, you're absolutely correct. But in this case, it still
sounds very likely: infinite recursion of a properly tail-recursive
function would loop rather than cause a stack overflow, which would
explain everything, except for why it's not actually an infinite loop;
I suspect the macOS code somewhere does modify things asynchronously.
next prev parent reply other threads:[~2020-01-08 20:39 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-26 9:47 bug#38748: 28.0.50; crash on MacOS 10.15.2 Andrii Kolomoiets
2019-12-26 13:04 ` Alan Third
2019-12-26 17:18 ` Eli Zaretskii
2019-12-27 11:28 ` Andrii Kolomoiets
2019-12-27 14:14 ` Eli Zaretskii
2019-12-29 19:01 ` Andrii Kolomoiets
2019-12-29 19:31 ` Eli Zaretskii
2020-01-01 20:42 ` Andrii Kolomoiets
2020-01-02 14:06 ` Eli Zaretskii
2020-01-08 17:39 ` Robert Pluim
2020-01-08 19:18 ` Pip Cet
2020-01-08 19:58 ` Eli Zaretskii
2020-01-08 20:39 ` Pip Cet [this message]
2020-01-09 3:30 ` Eli Zaretskii
2020-01-10 7:32 ` Pip Cet
2020-01-10 8:27 ` Eli Zaretskii
2020-01-10 8:58 ` Robert Pluim
2020-01-10 9:21 ` Eli Zaretskii
2020-01-10 10:18 ` Robert Pluim
2020-01-11 6:26 ` Pankaj Jangid
2020-01-11 8:08 ` Eli Zaretskii
2020-01-11 10:43 ` Pankaj Jangid
2020-01-11 12:14 ` Eli Zaretskii
2020-01-10 9:22 ` Pip Cet
2020-01-10 9:33 ` Eli Zaretskii
2020-01-11 13:59 ` Alan Third
2020-01-11 14:13 ` Pip Cet
2020-01-11 19:07 ` Alan Third
2020-01-08 21:43 ` Robert Pluim
2020-01-08 22:18 ` Pip Cet
2020-01-08 22:23 ` Robert Pluim
2020-01-09 7:51 ` Robert Pluim
2020-01-09 10:07 ` Eli Zaretskii
2020-01-09 10:31 ` Robert Pluim
2020-01-09 14:10 ` Pip Cet
2020-01-09 14:16 ` Eli Zaretskii
2020-01-09 14:56 ` Robert Pluim
2020-01-09 17:06 ` Eli Zaretskii
2020-01-09 13:51 ` Andrii Kolomoiets
2020-01-09 14:13 ` Robert Pluim
2020-01-09 14:16 ` Pip Cet
2020-01-09 14:29 ` Andrii Kolomoiets
2020-01-09 15:15 ` Robert Pluim
2020-01-11 18:37 ` Pieter van Oostrum
2020-01-11 18:43 ` Eli Zaretskii
2020-01-11 21:23 ` Pieter van Oostrum
2020-01-12 3:33 ` Eli Zaretskii
2020-01-11 19:14 ` Pip Cet
2020-01-11 21:36 ` Pieter van Oostrum
2020-01-04 16:48 ` Pieter van Oostrum
2020-01-04 17:25 ` Alan Third
2020-01-05 19:41 ` Pieter van Oostrum
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='CAOqdjBc8kN-nb=4qf7hUd-9sPD0cae75j7SnKpN-K25pY=FVHQ@mail.gmail.com' \
--to=pipcet@gmail.com \
--cc=38748@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=andreyk.mad@gmail.com \
--cc=eliz@gnu.org \
--cc=jguenther@gmail.com \
--cc=rpluim@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.