This is the mail archive of the
dwarf2@corp.sgi.com
mailing list for the dwarf2 project.
Re: DWARF references crossing shared library boundaries
- To: eager at eagercon dot com
- Subject: Re: DWARF references crossing shared library boundaries
- From: todd dot allen at ccur dot com (Todd Allen)
- Date: Thu, 1 Mar 2001 14:09:20 -0700 (MST)
- Cc: dwarf2 at corp dot sgi dot com (dwarf2)
- Reply-To: todd dot allen at ccur dot com (Todd Allen)
>
> My first impression is that a shared library which contained a DW_FORM_ref_addr
> which was not resolved would have a relocation table entry. A debugger can
> resolve this reference when it reads the Dwarf data, since it generally
> has information about all of the shared libraries which are loaded.
>
> I don't see a problem with permitting DW_FORM_ref_addr to be unresolved
> in a shared library.
>
Yes, the debugger uses the leftover relocations in the shared object(s)
and static executable to do it.
--
Todd Allen
Concurrent Computer Corporation