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=1654639026;
	bh=0wF0nLI1QrquJhW6TxomtsT0Bb+2H/xg+y3X1MhVaM0=;
	h=X-UI-Sender-Class:Date:From:To:Subject:In-Reply-To:References;
	b=i3nwwkVgMIBMx/YQurCaOTsWLTvk0JolbOo/cyRhyb/MHDulajLb/6yj14ZHW28+H
	 V6GJFZV82QDxbhCpXefdN5Yzz+EGFiqJ3ul5JhzHJx8O3At+xm+F+pec2evcmJT90N
	 dpr3Ujg5xiVAZHN4p7v9RoZCxZWjZMUgHJ5OIcok=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Date: Tue, 7 Jun 2022 23:57:03 +0200
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: make crashing with SIGABRT error
Message-ID: <20220607235703.47369496@gmx.de>
In-Reply-To: <AM8P194MB1188A88B01FAFB3040F1FC70D0A39@AM8P194MB1188.EURP194.PROD.OUTLOOK.COM>
References: <AM8P194MB1188FE3DF74EF8428D1F5750D0A39 AT AM8P194MB1188 DOT EURP194 DOT PROD DOT OUTLOOK DOT COM>
	<AM8P194MB1188A88B01FAFB3040F1FC70D0A39 AT AM8P194MB1188 DOT EURP194 DOT PROD DOT OUTLOOK DOT COM>
X-Mailer: Claws Mail 3.18.0 (GTK+ 2.24.32; x86_64-suse-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
X-Provags-ID: V03:K1:TUWSNetrnKq5QcqXjCTViBci+QNbO3/8bdY0jBNikwNTbt8sF8h
 nSBFP6qzsREgwHr4z4ZXVGD293UY0Cs3jhpgXWxLlwnNyUShesunGsTZDcSrG+lkK0jXrrX
 7bOGDzNh8G6NQjPkrm6KyMhvObK83F3jQ9VTro/sVvzmIqaGxigTVpbXM+psjfaAJ6qdxrr
 IBBaETKdFvPUl46Lg4h6g==
X-Spam-Flag: NO
X-UI-Out-Filterresults: notjunk:1;V03:K0:QZLkGcWkMzE=:4gLZ/0b9QtJuVPGQ/d1TzX
 ctEcrkNTi1V6O6lpVfS1Jnvtjo54wp+nFvOQu7797n8tGIVgG+3qPOSA3rMu7VGCrDorNlmHN
 IC836Z9eVMzhWNahFPtD3Ilz6QuqXENRpl3piaynVAlIPOaeIOHdfRPKg8xYDy07P286kmZvv
 Ve93kiXGxqUMUzy/wtdaCqq+pBvy/FowcC1vrmv83JB83mZt47PTDweGHrI7VstAexRKdQthn
 WpN1lelnzMFq0sAaYO7tzG1hbBMoJhftkEDhT+JlE1FOshpGkBQrcAC5OFPtkxw/ltv+OkeEB
 NnNd7u3H1KM22IcR6CDngB50wunEc8z3MTQOv45BO9De2BnYhUGlAnO0Xs9Rp/2GjroFJ4I4y
 WC+IxJwyX75hyIRqHueum5QS1VI9T1xRh3NBMutiBZohrWsZJbDMz0VeIj7z1Z3fw9S0O7VlE
 J5wjED13EKla5xPDU0JWz8/cyY+KAifvvQdJ5bxonHYEEI4XBCAmO1DdBVsrjKkoGMg7jFW2M
 MWe9lrxBHgBoEqARA0pJ2hGXlNLOH46kEuTYd5MlCh3l+KmYe39cV4FWRQw42pj4XtdwDwQa7
 /02d0t04BN7HgUjgdCf3cipblkUjCsjdf4xjYYWTyRXKdhYn7FAhDhUQI1AVs+rJwX50sf5E1
 XNNlPsaEGP7PVZ9woHeVg/OFc4arpBClL59tlMHDj60p1upDIu8etvWA78KkDOyXsrJCMj02O
 pBBixaOwnl4KO5uszu/BVKoU0CzcugRIMbxp636TdbulofMoz90TNXvO3+dpgIYly+3FaVpFE
 3cvkJOBJjQLMerWd3ywglk/jyFeclt/SdCYjkraRBoN5uDi8MMdFnN3eXtWTFZ87sBh0pGipJ
 IwTiTh07/3TeB/RBnkygqJ0fmpg45mggM06N2B+FKkUQ8hhODS0I4BVTWlcLOuV9z66T+onw8
 yw1aOn56vVkNNLw7SASl0cLoMxu/H3hd6txfcJotQ+yHJpXQitq6M4plblTEi3RY/u/gNFYud
 zVHo+OGAj7fS2jxNKJA0X7xpCN8lPDd31CzdrWFR6qFtxdO4KSusLWyIuL6EmiZP4JRpiSaMO
 HlijZnrUO2FFgqPb1jIaHQKWRLUiPLCHqDIps/uLEOKA0HHE2M6lV1dUg==
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id 257LvBMB024630
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

Am Sun, 5 Jun 2022 15:12:45 +0000
schrieb "Patryk Matusiak (watermelonpl AT outlook DOT com) [via
djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>:

> How to fix make crashing with SIGABRT error on every platform I try
> to build something on? (Now, I'm trying on Windows XP Professional
> SP3 x86 and trying to build allegro lib to use with Watcom C)
>
[snip]

The size of the stack trace seems to indicate that make is in a
deep recursive call of functions.  Unter certain conditions still
unclear to me, this may lead to a punctual corruption of certain
tables used by the nmalloc system because local variables that
should be stored on stack are placed in the nmalloc tables.  Later
if a realloc() or a free() is issued, this table corruption is
detected by the nmalloc system rising the SIGABRT.  I do not have
neither the time nor the knowledge to fix this issue, so I have
decided to replace the make port by a new one that uses the old
malloc system used in djdev203.
If you are still interested, you can download it as:
  http://ftp.delorie.com/pub/djgpp/current/v2gnu/mak43br2.zip
and give it a try to see if this does really solve the issue.

I have compiled Allegro 4.2.2 in 2007-09-08 and uploaded the produced
zip files to ftp.delorie.com.  I do not remember what version of the
DJGPP toolchain I have used in those days, but as far as I remember
Allegro 4.2.2 was the last version with DOS/DJGPP support at all.
If a current version can be compiler with DJGPP or Watcom C is unclear
to me.  I assume that a major porting effort will be required.

Regards,
Juan M. Guerrero