From: Daniel Jacobowitz <drow@false.org>
To: Kalpana Ramamurthy <kal_pana@hotmail.com>
Cc: gdb@sourceware.org
Subject: Re: Errors in gdb6.4 "incomplete CFI data" and "const value lengthmismatch"
Date: Mon, 02 Apr 2007 10:53:00 -0000 [thread overview]
Message-ID: <20070402105307.GA30675@caradoc.them.org> (raw)
In-Reply-To: <BAY144-F123D3E3BFCFEA2364D835CE8600@phx.gbl>
On Mon, Apr 02, 2007 at 05:27:43AM +0000, Kalpana Ramamurthy wrote:
> >> I am using gdb 6.4. I get a lot of errors like
> >> >>During symbol reading, incomplete CFI data; unspecified registers (e.g.,
> >rax)
> >> >>at 0x1452fa.
> >> I also get errors like
> >It's not an error, just a warning.
> Why does it occur and how can I eliminate this problem ? Setting complaints=1
> gives me one
> instance of this warning. Setting complaints=20 gives me multiple instances of
> it. Maybe by understanding the root cause of this problem, I might be able to
> eliminate the warning completely.
Please search the archives for this list and gdb-patches, where it has
been discussed extensively.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-04-02 10:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 9:24 gdb 6.4 does not stop unwinding even after reaching the last frame Kalpana Ramamurthy
2007-03-28 11:26 ` Daniel Jacobowitz
2007-03-29 6:36 ` gdb 6.4 does not stop unwinding even after reaching the lastframe Kalpana Ramamurthy
2007-03-29 11:05 ` Daniel Jacobowitz
2007-03-30 10:47 ` Errors in gdb6.4 "incomplete CFI data" and "const value length mismatch" Kalpana Ramamurthy
2007-03-30 11:33 ` Daniel Jacobowitz
2007-04-02 5:27 ` Errors in gdb6.4 "incomplete CFI data" and "const value lengthmismatch" Kalpana Ramamurthy
2007-04-02 10:53 ` Daniel Jacobowitz [this message]
2007-04-16 11:26 ` Why does gdb print a complete stack trace even after switching to other frames ? Kalpana Ramamurthy
2007-04-16 11:37 ` Daniel Jacobowitz
2007-05-02 14:10 ` gdb 6.4 not allowing me to change the value of registers like $SP,$RBP and $RIP Kalpana Ramamurthy
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=20070402105307.GA30675@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