Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: Sachidananda Swain <sachidananda@kyocera-wireless.com>
Cc: Daniel Berlin <dan@cgsoftware.com>,
	steve.miller@st.com, Lan.Zhang@Zoran.com, gdb@sources.redhat.com,
	port-arm@NetBSD.org, gdb@sourceware.cygnus.com,
	Lin.Colin@iac.com.tw, grante@visi.com, gdb-discuss@gnu.org,
	davidm@snapgear.com, drow@false.org
Subject: Re: [Gdb-discuss] Dwarf Error: Cannot find referent at offset XXXXXX
Date: Wed, 08 Sep 2004 16:27:00 -0000	[thread overview]
Message-ID: <vt2n0009171.fsf@zenia.home> (raw)
In-Reply-To: <F21CE557E34E8340B6777F799626EB0DE8442A@kwisrv3.kwi.intra.kyocera-wireless.com>


Sachidananda Swain <sachidananda@kyocera-wireless.com> writes:
> I am working on GDB for debugging. Tried with all gdb version and in all
> cases I am getting Dwarf error. Please tell me how to overcome this error.
> What I feel that there may be mismatching of dwarf format between ads
> compiler and gdb. I saw so many numbers of people facing this problem. So
> tell be very frankly that this problem can be solved or not; otherwise I
> have to close this project because I am in a deadline. If any where I am
> doing mistake please tell me how to do this. Once I can able to communicate
> >From host with all commands then I will start writing gdb-stub for target
> side. I will be waiting for u r reply.

I'm not familiar with the ADS compiler; it may be generating Dwarf 2
information that GDB cannot handle.  The Dwarf 2 information in an
executable's .debug_info section is divided into a series of
"compilation units".  Each compilation unit is a tree of "DIEs"
(Debugging Information Entries)".  Dwarf 2 allows dies in one
compilation unit to point to dies in other compilation units, but GDB
does not support this yet.

You might try running 'readelf -wi' on your executable, and looking at
the die for the variable you're trying to print.  If it includes a
reference printed as '<#number>' instead of '<number>', then that is
an inter-compilation-unit reference.

If that is the case, then you might check out the GDB branch
"drow_intercu-20040221-branch" and try that debugger.  Follow the
instructions to login on this page:

  http://sources.redhat.com/gdb/current

and then check out the sources using this command:

  cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/src co -r drow_intercu-20040221-branch gdb+dejagnu

I'd be interested to see the output from 'readelf -wi'; if it's not
too huge, could you post it here?


           reply	other threads:[~2004-09-08 16:27 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <F21CE557E34E8340B6777F799626EB0DE8442A@kwisrv3.kwi.intra.kyocera-wireless.com>]

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=vt2n0009171.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=Lan.Zhang@Zoran.com \
    --cc=Lin.Colin@iac.com.tw \
    --cc=dan@cgsoftware.com \
    --cc=davidm@snapgear.com \
    --cc=drow@false.org \
    --cc=gdb-discuss@gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=gdb@sourceware.cygnus.com \
    --cc=grante@visi.com \
    --cc=port-arm@NetBSD.org \
    --cc=sachidananda@kyocera-wireless.com \
    --cc=steve.miller@st.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