From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10769 invoked by alias); 26 Jul 2002 17:07:03 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 10762 invoked from network); 26 Jul 2002 17:07:02 -0000 Received: from unknown (HELO uclink4.berkeley.edu) (128.32.25.39) by sources.redhat.com with SMTP; 26 Jul 2002 17:07:02 -0000 Received: from zhangl (p1.almaden.ibm.com [198.4.83.52]) by uclink4.berkeley.edu (8.12.3/8.12.3) with SMTP id g6QH70oj010566; Fri, 26 Jul 2002 10:07:01 -0700 (PDT) Message-ID: <005001c234c7$476c4790$9a0a0109@zhangl> From: "Lucy Zhang" To: "Jim Blandy" Cc: References: <011601c23443$26f32f80$9a0a0109@zhangl> Subject: Re: couldn't parse type message error Date: Fri, 26 Jul 2002 10:07:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-SW-Source: 2002-07/txt/msg00284.txt.bz2 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" To: "Lucy Zhang" Cc: Sent: Friday, July 26, 2002 10:02 AM Subject: Re: couldn't parse type message error > > "Lucy Zhang" 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?