This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [COMMIT] Fix decoding CIE's in DWARF frame info


   Date: Fri, 5 Nov 2004 15:41:02 -0500
   From: Daniel Jacobowitz <drow@false.org>

   > I don't think so.  We read the encoded pointers when we load the
   > executable in GDB.  But if the value of these encoded pointers is
   > known at that point, why doesn't the (static) linker resolve things
   > instead of having us goe through the indirection process?

   Because this is used, as far as I know, only for PIC code in shared
   libraries (which we only load after they've been dynamically
   relocated).  DW_EH_PE_indirect is used so that symbols which will need
   a runtime RELATIVE relocation live in the data segment, instead of the
   with the rest of the exception data, which could otherwise be read-only.

Hmm.  You might be right.  Didn't think about it that way.

Mark


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]