Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: pgilliam@us.ibm.com
Cc: gdb-patches@sourceware.org
Subject: Re: Use DWARF CFI frame unwinder on powerpc
Date: Tue, 09 May 2006 17:46:00 -0000	[thread overview]
Message-ID: <jeody7hz16.fsf@sykes.suse.de> (raw)
In-Reply-To: <1147195124.16180.44.camel@dufur.beaverton.ibm.com> (PAUL 	GILLIAM's message of "Tue, 09 May 2006 10:18:44 -0700")

PAUL GILLIAM <pgilliam@us.ibm.com> writes:

>>>>>During symbol reading, incomplete CFI data; unspecified registers
>>>>>(e.g., r0) at 0x10000464.

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.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


  parent reply	other threads:[~2006-05-09 17:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-09 14:16 Andreas Schwab
2006-05-09 17:17 ` PAUL GILLIAM
2006-05-09 17:23   ` Daniel Jacobowitz
2006-05-09 22:26     ` PAUL GILLIAM
2006-05-09 17:46   ` Andreas Schwab [this message]
2006-05-09 18:01     ` David S. Miller
2006-05-09 18:39       ` Daniel Jacobowitz
2006-05-09 21:07         ` David S. Miller
2006-05-15 16:46 ` Daniel Jacobowitz
2006-05-15 19:10   ` Mark Kettenis
2006-05-15 20:43     ` 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=jeody7hz16.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=gdb-patches@sourceware.org \
    --cc=pgilliam@us.ibm.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