P J P <pj.pandit@xxxxxxxxxxx> writes: > --- On Thu, 29/7/10, Ian Lance Taylor <iant@xxxxxxxxxx> wrote: >> The former. It is attached to a definition to mean >> that the definition is externally visible. > > Right. Then, should this flag be set for the variables/functions > coming from an outside object file through linking? > > Ex. Say an application uses standard library functions like malloc, > scanf, operator>>, operator<< etc. The dwarf DIEs describing such > symbols have the external flag set. > > Looking at the DIEs, is there any way of knowing which symbols are > defined in the same object file and which ones come from other object > files through linking? I don't think I understand the question. gcc does not normally generate debug info for library functions which are only referenced, not defined. Where is the debug info for these functions coming from? Ian
