.o files in namelist

[Perry Hutchison]

In article <20848 at adm.BRL.MIL> stanonik at 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.