Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!uunet!zephyr.ens.tek.com!tektronix!sequent!ccssrv!perry
From: perry@ccssrv.UUCP (Perry Hutchison)
Newsgroups: comp.unix.wizards
Subject: Re: .o files in namelist
Message-ID: <620@ccssrv.UUCP>
Date: 15 Sep 89 00:42:31 GMT
References: <20848@adm.BRL.MIL>
Reply-To: perry@ccssrv.UUCP (Perry Hutchison)
Organization: Control-C Software, Inc., Beaverton, OR
Lines: 14

In article <20848@adm.BRL.MIL> stanonik@nprdc.navy.mil (Ron Stanonik) writes:

>Why does the namelist include the names of the .o files making
>up the object?  For example ...

>	00000d88 t ioctl.o
    <others deleted>
>
>Are these just to record which files made up the object?  Do any
>programs depend upon this information?

Source-level debuggers can use these entries to figure out which object file
contained a particular function.  They then can deduce the probable name of
the source file.