Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Fabian Cenedese <Cenedese@indel.ch>
To: gdb@sourceware.org
Subject: Re: symbol maintenance
Date: Wed, 29 Nov 2006 09:24:00 -0000	[thread overview]
Message-ID: <5.2.0.9.1.20061129100307.018934f0@NT_SERVER> (raw)
In-Reply-To: <m3ejrntl1g.fsf@codesourcery.com>


>>>> (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.

I uploaded the output (11MB uncompressed, 1MB zipped) here:
http://www.speedyshare.com/512483789.html

I looked for the definition of this mismatch variable in the source. It's:

typedef signed char int8;
const int8 ciOffline = 254;

254 for a signed char is not really nice, but that alone shouldn't
confuse gdb or gcc, right?

 <2><6774b>: Abbrev Number: 92 (DW_TAG_variable)
     DW_AT_name        : ciOffline      
     DW_AT_decl_file   : 6      
     DW_AT_decl_line   : 142    
     DW_AT_type        : <685a0>        
     DW_AT_external    : 1      
     DW_AT_declaration : 1      
     DW_AT_const_value : 8 byte block: ff ff ff ff ff ff ff fe  

I don't know what variable or entry would cause the "unsupported const
value attribute form:'DW_FORM_string'", I can't find that string.

Thanks

bye  Fabi



  reply	other threads:[~2006-11-29  9:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-24 13:44 Fabian Cenedese
2006-11-27 21:30 ` Jim Blandy
2006-11-28 11:39   ` Fabian Cenedese
2006-11-28 19:42     ` Jim Blandy
2006-11-29  9:24       ` Fabian Cenedese [this message]
2006-11-29 10:55       ` Fabian Cenedese
2006-11-29 11:04         ` Fabian Cenedese

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5.2.0.9.1.20061129100307.018934f0@NT_SERVER \
    --to=cenedese@indel.ch \
    --cc=gdb@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox