Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alan Modra <amodra@bigpond.net.au>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: Jim Blandy <jimb@red-bean.com>,
	binutils@sourceware.org, 	gdb-patches@sourceware.org
Subject: Re: linker debug info editing
Date: Mon, 13 Mar 2006 20:19:00 -0000	[thread overview]
Message-ID: <20060313062335.GR6777@bubble.grove.modra.org> (raw)
In-Reply-To: <1142217868.20401.15.camel@linux.site>

On Sun, Mar 12, 2006 at 09:44:27PM -0500, Daniel Berlin wrote:
> On Fri, 2006-03-10 at 17:44 -0800, Jim Blandy wrote:
> > After you've chosen dies to delete, how do you deal with other dies
> > that refer to the deleted dies?  I'm not talking about parents; I'm
> > talking about attributes whose form is DW_FORM_ref*.
> 
> The only correct answer to this is "rewrite all the references all
> starting from scratch" :P

Yes, that's the conclusion I was coming to..  It's a pain.  All the
offsets can change, and in some cases there can even be an increase.
eg. rewriting a DW_FORM_ref2 as a DW_FORM_ref_addr, to point 
at the proper info (that for the kept function).  I think all the info
is there for ld to do this, but it's quite a lot more work than I
realized.  When I started, I knew more about how to do this in ld than
what actually needed doing.  :)

-- 
Alan Modra
IBM OzLabs - Linux Technology Centre


  reply	other threads:[~2006-03-13  6:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-10 19:44 Alan Modra
2006-03-10 20:06 ` James E Wilson
2006-03-10 20:16   ` Daniel Jacobowitz
2006-03-12  7:58 ` Jim Blandy
2006-03-13 12:53   ` Daniel Berlin
2006-03-13 20:19     ` Alan Modra [this message]
2006-03-14 15:10     ` Daniel Berlin
2006-03-13  4:59 ` Daniel Jacobowitz

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=20060313062335.GR6777@bubble.grove.modra.org \
    --to=amodra@bigpond.net.au \
    --cc=binutils@sourceware.org \
    --cc=dberlin@dberlin.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jimb@red-bean.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