From: Jim Blandy <jimb@redhat.com>
To: "Lucy Zhang" <lucyz@uclink4.berkeley.edu>
Cc: <gdb@sources.redhat.com>
Subject: Re: couldn't parse type message error
Date: Fri, 26 Jul 2002 10:02:00 -0000 [thread overview]
Message-ID: <npd6tas9qo.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <011601c23443$26f32f80$9a0a0109@zhangl>
"Lucy Zhang" <lucyz@uclink4.berkeley.edu> writes:
> When I'm using GDB, i.e. using print/x, I get the message:
> "During symbol reading, couldn't party type: debugger out of date?"
>
> Does anyone know why i'm getting this. Despite the message, all the
> information still gets printed. Just wondering what is causing this printout
> and if it can be fixed.
The debugging information in the executable is broken up by
compilation units (i.e., .o files). GDB does an initial scan, but
puts off really reading each compilation unit's debug info until it
needs it. When it does decide to read the info, it reads a full
compilation unit's info at a time (and maybe some other CUs', in some
cases).
So your print command is causing GDB to read some compilation unit's
debug info, and in the process, GDB comes across a type that it can't
parse.
What compiler and debugger are you using? Which versions?
next prev parent reply other threads:[~2002-07-26 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 18:21 Lucy Zhang
2002-07-26 10:02 ` Jim Blandy [this message]
2002-07-26 10:07 ` Lucy Zhang
[not found] ` <npsn26qrep.fsf@zwingli.cygnus.com>
2002-07-26 14:09 ` Lucy Zhang
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=npd6tas9qo.fsf@zwingli.cygnus.com \
--to=jimb@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=lucyz@uclink4.berkeley.edu \
/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