stanonik@nprdc.navy.mil (Ron Stanonik) (09/14/89)
Why does the namelist include the names of the .o files making up the object? For example, nm an unstripped program and you'll see entries such as: 00000d88 t ioctl.o 00000d64 t isatty.o 00000d98 t malloc.o 00000068 t printf.o 000010a0 t sbrk.o 00000000 T start 00000054 t test.o 000010d0 t write.o Are these just to record which files made up the object? Do any programs depend upon this information? Thanks, Ron Stanonik stanonik@nprdc.navy.mil
perry@ccssrv.UUCP (Perry Hutchison) (09/15/89)
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.