Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: ppmoore <polomora@gmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: Get >incomplete type> when I try to display a variable
Date: Wed, 07 Mar 2007 15:49:00 -0000	[thread overview]
Message-ID: <20070307154910.GA13899@caradoc.them.org> (raw)
In-Reply-To: <9355446.post@talk.nabble.com>

On Wed, Mar 07, 2007 at 07:47:23AM -0800, ppmoore wrote:
> I'm now debugging another section of code where the .c and the .h files are
> in separate directories. As before, I copy these across to the executable
> location. When I debug, I get the error <incomplete type> when I try to
> examine the contents of a structure or pointer to a structure. Is this
> because in the development enviromnent, the .h and .c files are in different
> directories?

No, it has nothing to do with that.

Either some file was not compiled with -g, or your compiler has
omitted some necessary debug info.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-03-07 15:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-07 15:47 ppmoore
2007-03-07 15:49 ` Daniel Jacobowitz [this message]
2007-03-07 18:52 ` ppmoore

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=20070307154910.GA13899@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=polomora@gmail.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