From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10880 invoked by alias); 2 Apr 2007 10:53:12 -0000 Received: (qmail 10867 invoked by uid 22791); 2 Apr 2007 10:53:11 -0000 X-Spam-Check-By: sourceware.org Received: from return.false.org (HELO return.false.org) (66.207.162.98) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 02 Apr 2007 11:53:09 +0100 Received: from return.false.org (localhost [127.0.0.1]) by return.false.org (Postfix) with ESMTP id DB8444B267; Mon, 2 Apr 2007 05:53:07 -0500 (CDT) Received: from caradoc.them.org (dsl093-172-095.pit1.dsl.speakeasy.net [66.93.172.95]) by return.false.org (Postfix) with ESMTP id AE7CF4B262; Mon, 2 Apr 2007 05:53:07 -0500 (CDT) Received: from drow by caradoc.them.org with local (Exim 4.63) (envelope-from ) id 1HYK9r-00084A-7J; Mon, 02 Apr 2007 06:53:07 -0400 Date: Mon, 02 Apr 2007 10:53:00 -0000 From: Daniel Jacobowitz To: Kalpana Ramamurthy Cc: gdb@sourceware.org Subject: Re: Errors in gdb6.4 "incomplete CFI data" and "const value lengthmismatch" Message-ID: <20070402105307.GA30675@caradoc.them.org> Mail-Followup-To: Kalpana Ramamurthy , gdb@sourceware.org References: <20070330113253.GA5861@caradoc.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.14+cvs20070313 (2007-03-13) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-04/txt/msg00008.txt.bz2 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