couldn't parse type message error

couldn't parse type message error

[Lucy Zhang]

Hi,

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.

Thanks,
Lucy

Re: couldn't parse type message error

[Jim Blandy]

"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?

Re: couldn't parse type message error

[Lucy Zhang]

I'm using GCC for compiling and GDB 5.2.

I didn't use to get these printout message with the older version of GDB 5.0

I just find it weird since things gets printed out correctly, as far as i
know, despite this message

lucy
----- Original Message -----
From: "Jim Blandy" <jimb@redhat.com>
To: "Lucy Zhang" <lucyz@uclink4.berkeley.edu>
Cc: <gdb@sources.redhat.com>
Sent: Friday, July 26, 2002 10:02 AM
Subject: Re: couldn't parse type message error


>
> "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?

Re: couldn't parse type message error

[Lucy Zhang]

Hi,

could the printout be due to the fact I didn't use -g when compiling the
file with that variable?

lucy
----- Original Message -----
From: "Jim Blandy" <jimb@redhat.com>
To: "Lucy Zhang" <lucyz@uclink4.berkeley.edu>
Sent: Friday, July 26, 2002 11:23 AM
Subject: Re: couldn't parse type message error


> "Lucy Zhang" <lucyz@uclink4.berkeley.edu> writes:
> > I'm using GCC for compiling and GDB 5.2.
> >
> > I didn't use to get these printout message with the older version of GDB
5.0
> >
> > I just find it weird since things gets printed out correctly, as far as
i
> > know, despite this message
>
> Sorry, I didn't finish my explanation:
>
> Since GDB always reads in a whole compilation unit's debug info at a
> time, that message is probably complaining about the type of some
> other object it found in the same compilation unit.  But it was able
> to read the type of your object just fine, apparently.
>
> I realize it's odd that GDB responds to a request to print a variable
> by printing a warning message about something unrelated to that
> variable.  That's just the way it works.
>
> > lucy
> > ----- Original Message -----
> > From: "Jim Blandy" <jimb@redhat.com>
> > To: "Lucy Zhang" <lucyz@uclink4.berkeley.edu>
> > Cc: <gdb@sources.redhat.com>
> > Sent: Friday, July 26, 2002 10:02 AM
> > Subject: Re: couldn't parse type message error
> >
> >
> > >
> > > "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?