Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!sri-spam!ames!ucbcad!ucbvax!decvax!tektronix!uw-beaver!cornell!batcomputer!prove
From: prove@batcomputer.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: Re: Bug in Microsoft C 4.00?
Message-ID: <208@batcomputer.tn.cornell.edu>
Date: Wed, 18-Feb-87 20:02:13 EST
Article-I.D.: batcompu.208
Posted: Wed Feb 18 20:02:13 1987
Date-Received: Fri, 20-Feb-87 06:48:21 EST
References: <216700008@orstcs.UUCP> <216700009@orstcs.UUCP> <2395@homxb.UUCP>
Organization: Theory Center, Cornell U., Ithaca NY
Lines: 17
Summary: MSC & asm bug ?

In article <2395@homxb.UUCP>, gemini@homxb.UUCP (Rick Richardson) writes:
> In article <216700009@orstcs.UUCP>, go@orstcs.UUCP (go) writes:
> > Anyway, the attempt was to show a bug (which I cannot seem to demonstrate
> > with a simple program) that caused two arrays to share space.
> 
> There is a bug in the linker, somewhere.  I can't be sure, but I
> had the same problem when I mixed assembler and MS 4.0.  Some of the
> assembler declared variables ended up loaded over the top of the

This problem sounds familiar to me too, at least the part about wierd
problems in linking asm to MS C (v3 or 4).  Adding irrelevent printf's
would make the difference between a program that functioned normally
and one that crashed on startup.  The problem seemed to be that 
segments in the asm program have to be declared byte aligned.  Since
doing this I have had no problems.  I would have thought that the linker 
would catch any inconsistancy like this.  There also seems to be no
mention of such a requirement in the msc manual (v3).