Date:	Tue, 9 Jan 2001 09:54:17 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Robert van der Boon <rjvdboon AT europe DOT com>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: patch.exe (fwd)
In-Reply-To:	<000701c079ab$ccf8cd80$f8344bd5@robert>
Message-ID:	<Pine.SUN.3.91.1010109095357.19017B-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 8 Jan 2001, Robert van der Boon wrote:

> > > The error message I'm getting (patch 2.5.3, LFN=y, patch < news.diff ) is:
> > > patch: **** Can't rename file "C:\WINNT\TEMP/poaaaaaa" to "news.txt" : Not
> > > enough memory (ENOMEM)
> > 
> > Thanks for testing, that's what I suspected.
> > 
> > If you have some time to spare to dig into this, I could suggest several 
> > ideas to try.  It would be nice to solve this.
> 
> Sure. The only(?) problem is that the W2K machine I tested this was
> at work, with no DJGPP environment whatsoever... (But that can
> easily change)
> 
> Current DJGPP environment at home (and tomorrow at work ;-):
> DJGPP 2.03 Simtel-distro
> GCC 2.95.2
> BINUTILS 2.10
> and a whole bunch of tools.
> 
> If you can give directions on what to look for, and things to
> try, I'm willing to check them out.

First step would be to rebuild Patch from sources with the development
environment you have, and see that the problem persists.  (The binary
on SimTel was compiled with GCC 2.7.2.1 and Binutils 2.9.1; I doubt
that this will change anything, but better be safe than sorry.)

Since W2K doesn't like nested DJGPP programs, you will have hard time
building with Make, unfortunately.  One way to work around this is to
invoke "make -n > buid.bat", then run the batch file from the command
line, perhaps after some editing (e.g., to overcome the 126-character
limit of command lines).  Another possibility is to build on another
machine and copy binaries.

I suggest to make sure -g is in CFLAGS when you build; if not, add
it.

Once you have a debuggable binary that reproduces the problem, please
run it under a debugger and see what happens where `rename' is called.

Next step after that is to paste the sources of `rename' and `_rename'
into Patch sources, rebuild Patch, and step with a debugger into these
functions to see what exactly fails there.  (You might as well use the
latest CVS sources for these two functions, in case they already solve
some problems.)

TIA

- Raw text -