From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9115 invoked by alias); 26 Jul 2002 17:02:42 -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 9101 invoked from network); 26 Jul 2002 17:02:41 -0000 Received: from unknown (HELO zwingli.cygnus.com) (208.245.165.35) by sources.redhat.com with SMTP; 26 Jul 2002 17:02:41 -0000 Received: by zwingli.cygnus.com (Postfix, from userid 442) id BFCA65EA11; Fri, 26 Jul 2002 12:02:39 -0500 (EST) To: "Lucy Zhang" Cc: Subject: Re: couldn't parse type message error References: <011601c23443$26f32f80$9a0a0109@zhangl> From: Jim Blandy Date: Fri, 26 Jul 2002 10:02:00 -0000 In-Reply-To: <011601c23443$26f32f80$9a0a0109@zhangl> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-07/txt/msg00282.txt.bz2 "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?