Path: utzoo!attcan!uunet!mailrus!iuvax!bobmon
From: bobmon@iuvax.cs.indiana.edu (RAMontante)
Newsgroups: comp.sys.ibm.pc.programmer
Subject: Re: Microsoft C, 5.1 bug???
Message-ID: <46517@iuvax.cs.indiana.edu>
Date: 2 Jun 90 15:24:27 GMT
References: <90152.034339TOMIII@MTUS5.BITNET>
Reply-To: bobmon@iuvax.cs.indiana.edu (RAMontante)
Organization: malkaryotic
Lines: 19

TOMIII@MTUS5.BITNET (Thomas Dwyer III) <90152.034339TOMIII@MTUS5.BITNET> :
-I believe there is a bug in MSC 5.1  The following code demonstrates
-	[ simple routine to invoke a subshell ]
-Running this program under IBM DOS 3.3 results in COMMAND.COM being
-invoked, as expected, with "OOG=BLA" in it's environment.  However,
-the new environment not only has that string, but also a string of
-garbage at the end.  This garbage string ";C_FILE_INFO$$$$AA" (where
-$$$$ = 4 IBM funky characters, ASCII 05, 193, 193, 193) shows up on
-every machine the program was run on (True blue PCs and Zenith 386-30)
-even when recompiled.


I think this is intentional behavior on MSC's part, even prior to v5.1
My Procomm2.4.2, for example, has exactly the same behavior when I shell
out (this caused me some confusion at one time); Procomm2.4.2 was compiled
with a 1985-vintage MSC...  The string ";C_FILE_INFO" appears in three
different (nearby) places in the procomm.exe file, seemingly it is marking
some area of the executable.  (BTW, my "funky characters" are ASC 193,193,
193,1; and they aren't part of the string as stored in the executable.)