From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23482 invoked by alias); 9 May 2006 18:01:31 -0000 Received: (qmail 23407 invoked by uid 22791); 9 May 2006 18:01:25 -0000 X-Spam-Check-By: sourceware.org Received: from dsl027-180-168.sfo1.dsl.speakeasy.net (HELO sunset.davemloft.net) (216.27.180.168) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 09 May 2006 18:01:15 +0000 Received: from localhost ([127.0.0.1] ident=davem) by sunset.davemloft.net with esmtp (Exim 4.60) (envelope-from ) id 1FdWVN-0006c4-Rx; Tue, 09 May 2006 11:00:17 -0700 Date: Tue, 09 May 2006 18:01:00 -0000 Message-Id: <20060509.110014.123240405.davem@davemloft.net> To: schwab@suse.de Cc: pgilliam@us.ibm.com, gdb-patches@sourceware.org Subject: Re: Use DWARF CFI frame unwinder on powerpc From: "David S. Miller" In-Reply-To: References: <1147195124.16180.44.camel@dufur.beaverton.ibm.com> X-Mailer: Mew version 4.2.53 on Emacs 21.4 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-05/txt/msg00171.txt.bz2 From: Andreas Schwab Date: Tue, 09 May 2006 19:46:13 +0200 > That is presumably a gcc problem: > > /* NOTE: cagney/2003-09-05: CFI should specify the disposition > of all debug info registers. If it doesn't, complain (but > not too loudly). It turns out that GCC assumes that an > unspecified register implies "same value" when CFI (draft > 7) specifies nothing at all. Such a register could equally > be interpreted as "undefined". Also note that this check > isn't sufficient; it only checks that all registers in the > range [0 .. max column] are specified, and won't detect > problems when a debug info register falls outside of the > table. We need a way of iterating through all the valid > DWARF2 register numbers. */ > > Andreas. I really think this warning message should be off by default, 9 times out of 10 when it triggers the situation is completely harmless.