Date: Thu, 24 May 2001 09:38:41 +0300 (IDT) From: Eli Zaretskii X-Sender: eliz AT is To: Norberto Alfredo Bensa cc: djgpp-workers AT delorie DOT com Subject: Re: win2000/ntvdm/djgpp (fwd) In-Reply-To: <00af01c0e409$d299b060$0100a8c0@fibertel.com.ar> 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 Thu, 24 May 2001, Norberto Alfredo Bensa wrote: > What should I do? What I mean is: > > 1st... Apply patch to djdev203 > 2nd... Recompile > > and then, how should I test this? - apply patch to djlsr203 - rebuild the library - build Make and, maybe, gcc with the new library - run rebuilt programs nested more than 2 levels deep, and see if NTVDM crashes. Possible tests: * create a Makefile which invokes Make recursively, several levels deep. * compile a program, possibly with nested Make's. The patches I posted should prevent crashes in NTVDM even if you run old binaries (built without the patches), provided that the the old binaries are never nested more than 2 levels deep. In other words, you could try compiling from within a patched Make even with the old GCC binary, and it shouldn't crash. I think. Since rebuilding Make is much easier than rebuilding GCC, you could start testing the patches after rebuilding only Make. Thanks in advance for working on this.