Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Mattias Bertilsson <mattias.bertilsson@enea.com>
Cc: gdb@sourceware.org, binutils@sourceware.org
Subject: Re: Problem with gdb relocation of debug info
Date: Tue, 20 Jun 2006 12:37:00 -0000	[thread overview]
Message-ID: <20060620123332.GF20079@nevyn.them.org> (raw)
In-Reply-To: <4493F8EC.8040106@enea.com>

On Sat, Jun 17, 2006 at 02:43:24PM +0200, Mattias Bertilsson wrote:
> ld -o [exe] [intermediate] -T [lcf] -n --emit-relocs -e [crt0] --cref 
> --discard-none -M

This is the key.

As Andreas said, gdb is doing the right thing.  But you don't want it
to do that right thing.  You might want to prevent GDB from applying
relocations in ET_EXEC files - I presume this produces an ET_EXEC file.

-- 
Daniel Jacobowitz
CodeSourcery


      parent reply	other threads:[~2006-06-20 12:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-17 13:14 Mattias Bertilsson
2006-06-17 15:35 ` Andreas Schwab
     [not found]   ` <4494179C.9010401@enea.com>
2006-06-17 18:47     ` Andreas Schwab
2006-06-20 12:37 ` Daniel Jacobowitz [this message]

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=20060620123332.GF20079@nevyn.them.org \
    --to=drow@false.org \
    --cc=binutils@sourceware.org \
    --cc=gdb@sourceware.org \
    --cc=mattias.bertilsson@enea.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