X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Received: by 10.200.39.104 with SMTP id h37mr2611887qth.21.1515178713591; Fri, 05 Jan 2018 10:58:33 -0800 (PST) X-Received: by 10.31.48.85 with SMTP id w82mr389018vkw.11.1515178713103; Fri, 05 Jan 2018 10:58:33 -0800 (PST) Newsgroups: comp.os.msdos.djgpp Date: Fri, 5 Jan 2018 10:58:32 -0800 (PST) In-Reply-To: <588dc9f5-6ab8-4c5f-bc3b-92145d963da5@googlegroups.com> Complaints-To: groups-abuse AT google DOT com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=134.3.95.160; posting-account=OsAajgoAAADdKJnkJkmhzqP0jo6I_P_0 NNTP-Posting-Host: 134.3.95.160 References: <201710221615 DOT v9MGFXwU030968 AT delorie DOT com> <588dc9f5-6ab8-4c5f-bc3b-92145d963da5 AT googlegroups DOT com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <2d10f641-cc7e-48c9-90bb-c5b817a15a54@googlegroups.com> Subject: Re: ANNOUNCE: DJGPP port of GNU Gawk 4.2.0 uploaded. From: "Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT de) [via djgpp AT delorie DOT com]" Injection-Date: Fri, 05 Jan 2018 18:58:33 +0000 Content-Type: text/plain; charset="UTF-8" Bytes: 4695 Lines: 73 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp 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 Freitag, 5. Januar 2018 03:52:38 UTC+1 schrieb rug DOT DOT DOT AT gmail DOT com: > Hi, > > On Sunday, October 22, 2017 at 11:16:10 AM UTC-5, Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT hates DOT spam) [via djgpp-announce AT delorie DOT hates DOT spam] wrote: > > > > This is a port of GNU Gawk 4.2.0 to MSDOS/DJGPP. > > > > Send Gawk specific bug reports to . > > Send suggestions and bug reports concerning the DJGPP port > > to comp.os.msdos.djgpp or . > > I'm not fluent in AWK at all. In fact, my use of it is very fleeting, > mainly out of curiosity. But GAWK does have a very good manual. > > I was converting PSR Invaders (MASM syntax) to various other host > assemblers with scripts. Most of my scripts were using sed (Cheap > or GNU), but I did write one AWK script, too. > > * http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/pkg-html/psrinvad.html > * http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/games/psrinvad.zip > > I've still been playing around locally, making minor improvements, but > it seems latest DJGPP GAWK crashes (while older 4.1.1 works fine, same > as other DOS AWKs). I even did a quick rebuild of GAWK on Linux, but no > bug was found. So I assume this is a DJGPP-specific bug / regression. > > At first I thought it was my new script, that maybe I was doing something > weird. But no, even my old script (in .ZIP mentioned at above URL) > is borking. > > **************************************************************** > [ GCC 7.2.0 / DJGPP 2.05 ] G:\TONY>gawk -f inv-a86.awk invaders.asm > Assertion failed at field.c line 350, function purge_record: (fields_arr[i]->fla > gs & MALLOC) == 0 ? fields_arr[i]->valref == 1 : true > Exiting due to signal SIGABRT > Raised at eip=0008609c > eax=0014c3f0 ebx=00000120 ecx=00000000 edx=00000000 esi=00154054 edi=0017c778 > ebp=0014c4a8 esp=0014c3e0 program=C:\C\DJGPP\BIN\GAWK.EXE > cs: sel=00a7 base=00400000 limit=001cffff > ds: sel=00af base=00400000 limit=001cffff > es: sel=00af base=00400000 limit=001cffff > fs: sel=008f base=00007490 limit=0000ffff > gs: sel=00bf base=00000000 limit=0010ffff > ss: sel=00af base=00400000 limit=001cffff > App stack: [0014c6a0..000cc6a4] Exceptn stack: [000cbdc0..000c9e80] > > Call frame traceback EIPs: > 0x00085feb > 0x0008609c > 0x00073dfa > 0x0001f9bd > [ GCC 7.2.0 / DJGPP 2.05 ] G:\TONY>gawk --version | sed 1q > GNU Awk 4.2.0 > **************************************************************** > > I think the (valid!) line that is choking is this, but I don't know why: > > /NewInt9Hand.* PROC/,/NotIntercept:/ { if ($0 ~ /MOV/) { sub($2,"cs:&") } } > > So whatever. Just reporting this in case you know what to do with it. > It's no biggie to me, obviously. I almost hated to mention it, but .... I can reproduce this crash with gawk 4.2.0. I have rebuild today's gawk tarball (aka gawk-4.2.60.tar.gz) two times, one time using djdev205 and a second time using a freshly compiled libc.a version from today's CVS repository. Both port versions work flawlessly and do not crash. I have compared both outpufiles produced by the current port with both output files produced by gwk411b and I have found no differences. It seems to be a gawk regression that has already been fixed thus I have not investigated it futher. Regards, Juan M. Guerrero