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: Todd Allen <todd dot allen at ccur dot com>
- Subject: Re: DWARF references crossing shared library boundaries
- From: Michael Eager <eager at eagercon dot com>
- Date: Thu, 01 Mar 2001 11:30:42 -0800
- CC: dwarf2 <dwarf2 at corp dot sgi dot com>
- References: <200103010125.SAA61908@toad.ccur.com>
- Reply-To: Michael Eager <eager at eagercon dot com>
Todd Allen wrote:
>
> The biggest extension that we've made to DWARF 2.0.0 is to permit DWARF
> DW_FORM_ref_addr references to reference debugging information entries in
> another shared object.
> This deviates from the text in 7.5.4 discussing references of form
> DW_FORM_ref_addr, where it says "within the same executable or shared
> object". I'd like to loosen up that language.
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.
--
Michael Eager Eager Consulting eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077