X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
From: Andris Pavenis <pavenis AT latnet DOT lv>
To: djgpp-workers AT delorie DOT com
Subject: Re: Problems with long command lines in DJGPP
Date: Fri, 28 Jan 2005 10:53:29 +0200
User-Agent: KMail/1.7.91
References: <200501241804 DOT 18985 DOT pavenis AT latnet DOT lv> <200501260912 DOT 24266 DOT pavenis AT latnet DOT lv> <01c503d3$Blat.v2.4$75be0f60 AT zahav DOT net DOT il>
In-Reply-To: <01c503d3$Blat.v2.4$75be0f60@zahav.net.il>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200501281053.29722.pavenis@latnet.lv>
X-Virus-Scanned: by amavisd-new at fgi.fi
Reply-To: djgpp-workers AT delorie DOT com

On Wednesday 26 January 2005 20:17, Eli Zaretskii wrote:
> > From: Andris Pavenis <pavenis AT latnet DOT lv>
> > Date: Wed, 26 Jan 2005 09:12:24 +0200
> >
> > > > Tried. Initially it didn't compile (-Wall -W... -Werror) with
> > > > gcc-3.4.3.
> > >
> > > What were the warnings/errors, and how did you fix them?
> >
> > Some type casts due to comparison of signed and unsigned integers etc.
>
> The changes to fix that should probably be committed to the CVS.
>
> > So maybe really I should return to reallocating DOS memory block used to
> > pass command line.
>
> Yes, I think, on balance, this is the best way to fix the problem.
> Since that code worked for me at some point, I think it won't be hard
> to make it work again.

Well. There were additionally one wrong argument for _put_path2 which caused
failures after larger memory block were allocated (no more tbuf_beg==__tb).
After that command lines up to 64K seemed to mostly work, but there was still 
some occasional problems with my test example (I suspect some memory 
corruption). I didn't have time to look into that more detailed yet.

Andris