X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org;
	s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date:
	mime-version; bh=QEPKgkOFVGVv8snUTRWCeA6EPEn72af3FsHHCeNSw6U=; b=GodvULRmqvuU
	ieQWuwjycG6p8tlIemeyzV3Cv9pmDOTDKDtcPhBc6DyoOxLMqji66oknzWdqUOlDryxrCXD1J1AQf
	0HLg32cdFnvwPFJI961ViJ69r1GsKrx9CbQ2NSrx163PqmLXxLS+FHSMq5pyveukUZNxM5o89z0RI
	pgK1+z5JGgocF57xMicCVVkbPNYHzoRbw6Gd8DzGQ+auMWCpIroBkLUi0VzQdzst2Nt6I0AnRYVDU
	bapRDkDx/hxdc0XV+Ftq+kcDmiPdE8RsvDn7MkRmURr++P9booLlcv2W5xQkC191F+zxszwTrXHsy
	h15jde9TdUmMApKAoMTT4g==;
Date: Fri, 25 Feb 2022 08:53:48 +0200
Message-Id: <83sfs7qvwj.fsf@gnu.org>
From: "Eli Zaretskii (eliz AT gnu DOT org) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
To: djgpp AT delorie DOT com
In-Reply-To: <20220224215354.250d5149@gmx.de> (djgpp@delorie.com)
Subject: Re: Menu reference to nonexistent node error
References: <b84357c3-50cd-4b14-b88a-d55bdc8c58d1n AT googlegroups DOT com>
	<83a6eiu2dt DOT fsf AT gnu DOT org>
	<11cd86a4-05c0-4263-9cfc-ba6092388807n AT googlegroups DOT com>
	<838ru2tg43 DOT fsf AT gnu DOT org>
	<d88f70e8-26c0-4c46-b835-7bb34e735e35n AT googlegroups DOT com>
	<20220223204156 DOT 43b7d2e5 AT gmx DOT de>
	<4098c541-4be4-407b-8910-58e2915fc087n AT googlegroups DOT com>
	<20220224215354 DOT 250d5149 AT gmx DOT de>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> Date: Thu, 24 Feb 2022 21:53:54 +0100
> From: "Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT de) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
> 
> Am Thu, 24 Feb 2022 10:39:33 -0800 (PST)
> schrieb "Khusraw (mv DOT ionascu AT gmail DOT com) [via djgpp AT delorie DOT com]"
> <djgpp AT delorie DOT com>:
> 
> > Testing for longer I could note that there are crashes on both my
> > available "systems" when I use make 4.3 with gcc 3.4.6 too, though
> > not as frequent as with gcc 10.3.0. So I recommend the use of
> > make 4.1, I haven't seen yet any crash with it, and I tested it for
> > even longer.
> 
> I have observed the same.  As far as I can tell the issue is related to
> the nmalloc used in djdev205.  When I compile ports for DJGPP, I always
> use the current cvs repository code and replace the nmalloc stuff with
> the old malloc stuff.  This issue has been brought to my attention in:
>   https://www.delorie.com/archives/browse.cgi?p=djgpp/2020/05/01/00:19:09
> and I have tried to debug this for a couple of months but I fear that I
> am to dumb for this task.  It seems clear that after certain amount of
> memory consumption due to recursive call of certain functions in the
> make program certain nmalloc tables get corrupted.  I have given up to
> trace down this issue long time ago so do not ask me any details.

If nmalloc causes such hard-to-debug problems, I think we should go
back to the "old" malloc ASAP.  It makes no sense to me to produce
newer ports on such an unstable basis.