Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: cagney@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [COMMIT] Fix decoding CIE's in DWARF frame info
Date: Fri, 05 Nov 2004 20:53:00 -0000	[thread overview]
Message-ID: <200411052053.iA5KrgYS014739@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20041105204101.GA23606@nevyn.them.org> (message from Daniel Jacobowitz on Fri, 5 Nov 2004 15:41:02 -0500)

   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


  reply	other threads:[~2004-11-05 20:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-05 15:43 Mark Kettenis
2004-11-05 17:00 ` Andrew Cagney
2004-11-05 18:54   ` Mark Kettenis
2004-11-05 19:12     ` Daniel Jacobowitz
2004-11-05 20:37       ` Mark Kettenis
2004-11-05 20:41         ` Daniel Jacobowitz
2004-11-05 20:53           ` Mark Kettenis [this message]
2004-11-05 21:22     ` Andrew Cagney
2004-11-05 21:25       ` Daniel Jacobowitz
2004-11-05 22:00         ` Mark Kettenis
2004-11-05 22:11         ` Andrew Cagney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200411052053.iA5KrgYS014739@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=cagney@gnu.org \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox