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

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.

Regards,
Kalpana
====


>From: Daniel Jacobowitz <drow@false.org>
>To: Kalpana Ramamurthy <kal_pana@hotmail.com>
>CC: gdb@sourceware.org, kalpana.balaji@symphonysv.com
>Subject: Re: gdb registers multiple definition of symbols : patch to 
>fixthis
>Date: Tue, 31 Jul 2007 08:02:44 -0400
>
>On Tue, Jul 31, 2007 at 11:53:23AM +0000, Kalpana Ramamurthy wrote:
> > Why this patch is required with the code is compiled with gcc 3.4.6 is
> > something that I still don't
> > know.
>
>It sounds to me like your compiler is generating bogus information.
>
>--
>Daniel Jacobowitz
>CodeSourcery

_________________________________________________________________
Real Estate classifieds on MSN - for free.www.yello.in 
http://www.yello.in/home.php?utm_source=hotmailtag&utm_medium=email&utm_content=in&utm_campaign=jun


  reply	other threads:[~2007-08-01  4:45 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   ` Kalpana Ramamurthy [this message]
2007-08-01 11:21     ` gdb registers multiple definition of symbols : patch to fixthis 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=BAY144-F380471B57B4238983C93BAE8E80@phx.gbl \
    --to=kal_pana@hotmail.com \
    --cc=drow@false.org \
    --cc=gdb@sourceware.org \
    /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