GNU bug report logs - #38748
28.0.50; crash on MacOS 10.15.2

Previous Next

Full log

Message #62 received at 38748 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Pip Cet <pipcet <at> gmail.com>
Cc: rpluim <at> gmail.com, andreyk.mad <at> gmail.com, alan <at> idiocy.org,
 jguenther <at> gmail.com, 38748 <at> debbugs.gnu.org
Subject: Re: bug#38748: 28.0.50; crash on MacOS 10.15.2
Date: Thu, 09 Jan 2020 05:30:58 +0200

> From: Pip Cet <pipcet <at> gmail.com>
> Date: Wed, 8 Jan 2020 20:39:43 +0000
> Cc: rpluim <at> gmail.com, alan <at> idiocy.org, jguenther <at> gmail.com, 
> 	andreyk.mad <at> gmail.com, 38748 <at> debbugs.gnu.org
> 
> > 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.

The backtrace shows a very recursive GC, it doesn't show any other
function being deeply recursive.  So I'm not sure I understand what
tail-recursive function did you have in mind.  Can you elaborate?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.