This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: couldn't parse type message error
- From: Jim Blandy <jimb at redhat dot com>
- To: "Lucy Zhang" <lucyz at uclink4 dot berkeley dot edu>
- Cc: <gdb at sources dot redhat dot com>
- Date: 26 Jul 2002 12:02:39 -0500
- Subject: Re: couldn't parse type message error
- References: <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?