Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!mit-eddie!wuarchive!julius.cs.uiuc.edu!rpi!uupsi!fozzie!stanley
From: stanley@phoenix.com (John Stanley)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Gnu-awk (gawk) memory problems under MSDOS
Message-ID: <1a1RV2w163w@phoenix.com>
Date: 14 Jan 91 18:09:47 GMT
References: <35613@netnews.upenn.edu>
Organization: Not BIFF At All (NBAA)
Lines: 19

barron@desci.wharton.upenn.edu (Daniel Barron) writes:

> I'm writing a Gnu-awk (gawk) script on an IBM XT with MSDOS 3.3.
> It's designed to massage data from one program's output to another's
> input.  Problem is, each time a line is processed, about 10-15K of
> memory gets used (checked via system( "chkdsk" ) ).  After 25-30 lines
> I get
> 
> xalloc: no memory!
> 
> Help!  What could make my program gobble memory?  A bad function call?

   I ran into this, too. It looks like any piping (|) done in the
scripts gets buffered internally in awk, and it runs out of memory. When
I changed the design to "print >> file" then have DOS "dos-command <<
file" it cleared up. 

   Since there is a file involved in both cases, it really isn't a problem
to create one.