Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Kalpana Ramamurthy <kal_pana@hotmail.com>
Cc: gdb@sourceware.org
Subject: Re: gdb registers multiple definition of symbols : patch to fixthis
Date: Wed, 01 Aug 2007 11:21:00 -0000	[thread overview]
Message-ID: <20070801112057.GA10612@caradoc.them.org> (raw)
In-Reply-To: <BAY144-F380471B57B4238983C93BAE8E80@phx.gbl>

On Wed, Aug 01, 2007 at 04:44:58AM +0000, Kalpana Ramamurthy wrote:
> How do we verify the information generated by the compiler ? I wanted to see 
> all the definitions
> generated by the compiler for that symbol. How can I do that ? I couldn't 
> decipher anything
> with readelf and objdump.

Sorry, those are the tools you need to use.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2007-08-01 11:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-31 12:02 gdb registers multiple definition of symbols : patch to fix this Kalpana Ramamurthy
2007-07-31 17:16 ` Daniel Jacobowitz
2007-08-01  4:45   ` gdb registers multiple definition of symbols : patch to fixthis Kalpana Ramamurthy
2007-08-01 11:21     ` 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=20070801112057.GA10612@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=kal_pana@hotmail.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