gdb bug or corrupt dwarf info?

["Elmenthaler, Jens" <JENS.ELMENTHALER@advantest.com>]

Hi,

I'm currently investigation why gdb is only showing 'i' as local variable in the following loop body, and not also 'text':

 for (int i = 0; i < 5; i++) {
    const char *text = "sabel";
    cerr << "text=" << text << endl; // Suspended here
}

The corresponding output of objdump -W yields the following:

<2><74105>: Abbrev Number: 264 (DW_TAG_lexical_block)
     DW_AT_sibling     : <7411e>	
     DW_AT_ranges      : 0	
 <3><7410f>: Abbrev Number: 235 (DW_TAG_variable)
     DW_AT_name        : i	
     DW_AT_decl_file   : 1	
     DW_AT_decl_line   : 6962	
     DW_AT_type        : <23cd>	
     DW_AT_location    : 2 byte block: 91 68 	(DW_OP_fbreg: -24)
 <2><7411e>: Abbrev Number: 245 (DW_TAG_lexical_block)
     DW_AT_low_pc      : 0x7b108	
     DW_AT_high_pc     : 0x7b14c	
 <3><74128>: Abbrev Number: 235 (DW_TAG_variable)
     DW_AT_name        : text	
     DW_AT_decl_file   : 1	
     DW_AT_decl_line   : 6963	
     DW_AT_type        : <11f85>	
     DW_AT_location    : 2 byte block: 91 6c 	(DW_OP_fbreg: -20)

Contents of the .debug_ranges section:

    Offset   Begin    End
    00000000 0007b0dd 0007b0f2 
    00000000 0007b108 0007b156 
    00000000 <End of list>


So my question now is, whether this is a gdb bug which I possibly could fix, or whether the debug info is broken.

In my opinion it looks suspicious that the lexical block containing 'text' is not a child of the lexical block containing 'i', but a sibling.

Can someone provide a hint?

Greetings, Jens.