Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbatt!ihnp4!alberta!calgary!ingoldsby
From: ingoldsby@calgary.UUCP
Newsgroups: comp.sys.m6809
Subject: Re: C bugs
Message-ID: <916@vaxb.calgary.UUCP>
Date: Fri, 15-May-87 20:44:15 EDT
Article-I.D.: vaxb.916
Posted: Fri May 15 20:44:15 1987
Date-Received: Sat, 16-May-87 21:43:25 EDT
References: <1987May15.141952.4911@gpu.utcs.toronto.edu>
Organization: U. of Calgary, Calgary, Ab.
Lines: 27
Summary: Unresolved Refs

In article <1987May15.141952.4911@gpu.utcs.toronto.edu>, ac@gpu.utcs.toronto.edu (Mark Acfield) writes:
> 
> 
> 3) The final problem I had is one that I can't really put my finger on.
> I had added a bunch of diagnostic fprintf functions calls to my program.
> They were all very similar.  I had just copied them to various points
> in the program to dump out the value of certain variables I was interested
> in.  At one point I added a few more of these statements and started  
> getting all sorts of "unresolved references" from the linker.
> The solution seemed to be to remove some of the calls but I can't for the
> life of me see how the last few added fprintf's were any different than
> the earlier one.  Has anyone ever had any problems with unexplainable
> unresolved references?
>  
> -- 

Yes, and they puzzled me too.  In my case I discovered that one of the
passes of the compiler doesn't complain if it runs out of disk space.  The
output just seems to go to the great bit bucket in the sky.  Later on, after
the intermediate files have been deleted you are not aware that it ever ran
short of space.  The linker, however, can't find the last routines and
gives unresolved refs.  On my system, I find that making sure I have a
couple of hundred K free on the disk helps.  Then again, with R/S disks
you can't have a couple of hundred K free :>
                                             Terry

                                       ihnp4!alberta!calgary!ingoldsby