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; c=relaxed/simple; d=gmx.net;
	s=badeba3b8450; t=1645736037;
	bh=x+Mu4kKtYUcmfPyEpb7XMHMgo6Aq7yvItKpmWvuVR5Y=;
	h=X-UI-Sender-Class:Date:From:To:Subject:In-Reply-To:References;
	b=LoDxKR3ljRl9XkO/dCvGSkGZUXwiP/CzLS8rmN9uxi88fjsmhq63clnt/ERqLrMbA
	a7zttDYX8lBe54JM5KH7IlNFTpOgBg+uUgtJBComCns7Jfb33LfNbYsJ+zhkGJxW0Z
	nRUfCp5D9/bBkhSVo0YhDbfGsAe5xErOYDIG6SJU=
X-UI-Sender-Class:	01bb95c1-4bf8-414a-932a-4f6e2808ef9c
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>
To:	djgpp AT delorie DOT com
Subject:	Re: Menu reference to nonexistent node error
Message-ID:	<20220224215354.250d5149@gmx.de>
In-Reply-To:	<4098c541-4be4-407b-8910-58e2915fc087n@googlegroups.com>
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>
X-Mailer:	Claws Mail 3.18.0 (GTK+ 2.24.32; x86_64-suse-linux-gnu)
MIME-Version:	1.0
X-Provags-ID:	V03:K1:ILtLXYAlSzyIJOAaWo62fJFzbjIAUZIGUTA5tiaDb3C2EwfsNGe
	FUNzLdl5YAPubgQtRljmYOlltqBPNrNQuYekAFLDYmzdPVpOwFZnvBLaP2CCrTPGcGYVZyV
	wvy860ZvlRn44/56ArrUrhJwYEL0kdoT9Dcr1TBZK5UrU0jV7VyFChzDfFK9YALgLDGDwX7
	0Y4WQp+eTK4pXIl7//8jw==
X-Spam-Flag:	NO
X-UI-Out-Filterresults:	notjunk:1;V03:K0:r5fw2KAVp4o=:cdQNkbZp15Y3D4Wpq6Y6lR
	7/gjD5qesO0gRvSXU+eCS5+PG9RS9RCR57wOBRqJ+4Th+IOWjH+dnqveHgJMlRAyBuRyVB/Nc
	YTXYU6nQvXWbyzeMDNuL34fMgfFPatzYYHAbLdYRCK7sAFa+NXA3Uw7L0bv2L9CBvdf+ARE2/
	ltZeZPCFEoD9CGzrSoRvn1zoiTpRUtGggnWpLbpDGonaQe2lN3ASM/19Rp5O92lKHf3xfwJww
	vYFzl3Owq6BqLUoMqKiUoNk2fkWfE8J4Vox/JZYIqmnsV8GWX60g7k+bJpFGeii102fjWNL79
	42UHzvt6Tz1YffxKx4KdLMxTBdGfM3srxCjUq6TntNKCscL5gWacFV1+O4FPRDfNbWDZ9qDeo
	I0yec5RfcPm6F8Ayih7RpWodm1UT3oe6mcYC/9cVmBVxc0Wg4RDWc2704ARCSk+ZwKnKGRX9d
	A2Q8GBYknmH/uFgkcABMK2tA4yc26HQfhnDCCRS5I50gZ4gbH1sBgMCD34PPhCpDOKzxGmHWd
	IGI5KuXD67tYkXQLAJYk79M117TvfLtlgA70QL/dXrXDrL4wFzLqhZ58ofUGFDLRJpSwRz/rR
	4/CWrXMsRWo4WNBESMmHy5Ps0OgKcwfFBe+zkSRtjBKl8AThxn5ApWs0eqTwBviFgTMUkzAhO
	4tw12FrkIBseaNQXIcB9PKb+hFpHNJO1L5lGhW4xz1zgBsn0cWawnFbr9kkius1GOaZB7W1Se
	jqGtUPmM6epEKpT+MWND33om7xOLLtHXbU91qSV1WBEWhQEXNq95MyIUc3iynOToklGSlnFKi
	rYhElJ5En9GO2fYDeXF0Eq7wvUswEzvVeWLSZGnxkH0SvWXEunKsVl4C1E17tWyliytd5AzS0
	2RIRliIGZ8271qEYVyDPhSx6HCsaGMsZrU88AYzoN/jd03/S0A6ZFDdcRnFGn2RVftFgtbNrA
	abjyiT5nVRzJ5kPuhaE4rltdUgZC8pQHax9H5eC/C2JW+ME/RP7v4QCgpMVXo3mlRZ1r0Vbb3
	ZqlvNEgjve7mhpmgdlpofJtxcnKs0y93OTEPPsDMPjlUiRC/DrnahxP9WnKW1+pASOOKtCdMU
	W2K0mwHG489GHQ=
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id 21OKs1gD019944
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

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.  I
have forgotten about them but if you experience crashes of the make
program, you can try to trace down it by yourself.  The only thing you
need to do it to compile libc.a with -g -O0 and then compile the make
program with -g -O0 too.
The -O0 has absolute no impact on the crash.  It will crash anyway
under the right circumstances.  If not you can reproduced the bug as
described in the thread above.
Of course, this is not related only to the make program; som other
programs will exhibit the same memory failure under the right
circunstances too.  I have stoped using nmalloc at all because I do not
have the time to fix it and I have started to use the old malloc code
again in all the ports I have uploaded since then. I am not claiming
that the nmalloc is bad, I am simply telling that there is some subtle
bug in it that may be triggered under the right conditions.

Regards,
Juan M. Guerrero

- Raw text -