From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14852 invoked by alias); 28 Nov 2006 19:42:22 -0000 Received: (qmail 14841 invoked by uid 22791); 28 Nov 2006 19:42:21 -0000 X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (65.74.133.4) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 28 Nov 2006 19:42:13 +0000 Received: (qmail 26794 invoked from network); 28 Nov 2006 19:42:11 -0000 Received: from unknown (HELO localhost) (jimb@127.0.0.2) by mail.codesourcery.com with ESMTPA; 28 Nov 2006 19:42:11 -0000 To: Fabian Cenedese Cc: gdb@sourceware.org Subject: Re: symbol maintenance References: <5.2.0.9.1.20061124142829.017493c0@NT_SERVER> <5.2.0.9.1.20061124142829.017493c0@NT_SERVER> <5.2.0.9.1.20061128123045.0176cec0@NT_SERVER> From: Jim Blandy Date: Tue, 28 Nov 2006 19:42:00 -0000 In-Reply-To: <5.2.0.9.1.20061128123045.0176cec0@NT_SERVER> (Fabian Cenedese's message of "Tue, 28 Nov 2006 12:38:16 +0100") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-11/txt/msg00201.txt.bz2 Fabian Cenedese writes: >>> This is a gdb 6.5 cross-compiled with cygwin on WinXP for ppc. >>> >>> (gdb) file gccext3.x >>> Reading symbols from /data/gdb-6.5/gdb/gccext3.x...unknown symbol type 0x1e...ex >>> panding to full symbols...unsupported const value attribute form: 'DW_FORM_strin >>> g'...const value length mismatch for 'ciOffline', got 8, expected 0...done. >> >>Those look more serious. GDB is trying to read DWARF debugging >>information, and it's malformed. What compiler are you using? What >>does 'objdump -h gccext3.x' say? > > The used compiler is gcc 4.0.2, cross compiled for ppc. > The files for gccext3 were compiled with -gdwarf-2 (no +, no O). Oh, so you have an ELF file, not a PE file. In that case, could you run 'readelf -wi gccext3.x', and post the output? If the DWARF in that file is valid, and GDB's reading it properly, then the problem is that GCC is producing information GDB can't use. But even in that case, GDB should be able to properly skip data it doesn't understand (DWARF is very good about that), so the answer to your original question is, no, you don't need to worry about that warning --- unless you're trying to use string constants and GDB doesn't seem to know their values.