X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f Date: Wed, 12 Dec 2001 10:25:34 +0200 (IST) From: Eli Zaretskii X-Sender: eliz AT is To: Charles Sandmann cc: djgpp-workers AT delorie DOT com, acottrel AT ihug DOT com DOT au Subject: Re: go32-v2 memory chompage [was: Re: v2.03 refresh ...] In-Reply-To: <10112112033.AA16741@clio.rice.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Precedence: bulk On Tue, 11 Dec 2001, Charles Sandmann wrote: > > You are right, it probably is unsafe to make this change in the 2.03 > > refresh, since it's a needle in a haystack of other changes, and that > > area is tricky to change without breaking. > > > The problem with v2.03's dosexec is that if both foo and foo.exe are > > present, it runs foo via go32-v2 instead of running foo.exe. > > If someone knew the exact change that fixed this it might not be > hard to implement - but it's not in the comments of the code or the > cvs commits. I already looked at the code and the changes trying to figure that out, but couldn't. IIRC, there were several changes which did that, and they also changed other things, so it's hard to point out a single isolated change which would do. IIRC, the addition of the no-extension-search flag to the interpreters[] array was part of it, and another part was in the code in __spawnve (which now has parts of its code extracted into another function). It's possible that go32_exec was also changed a bit. I realize that the above probably doesn't help, but that's what I could glean from my feeble memory and the code in CVS. Perhaps Mark remembers the details: he did most of the work, while I just talked about that. As another possible source of info, you could browse the archives of this list; these issues were discussed at length at the time.