Displaying 7 results from an estimated 7 matches for "emitdie".
Did you mean:
emilie
2011 Apr 13
2
[LLVMdev] Extra padding on DWARF debug info?
DwarfDebug::emitDebugInfo() always appends four zero bytes to the tail
of the debug info section:
emitDIE(Die);
// FIXME - extra padding for gdb bug.
Asm->OutStreamer.AddComment("4 extra padding bytes for GDB");
Asm->EmitInt8(0);
Asm->EmitInt8(0);
Asm->EmitInt8(0);
Asm->EmitInt8(0);
Asm->OutStreamer.EmitLabel(Asm->GetTempSymbol("info_end&q...
2011 Apr 13
0
[LLVMdev] Extra padding on DWARF debug info?
On Apr 13, 2011, at 8:42 AM, Ken Dyck wrote:
> DwarfDebug::emitDebugInfo() always appends four zero bytes to the tail
> of the debug info section:
>
> emitDIE(Die);
> // FIXME - extra padding for gdb bug.
> Asm->OutStreamer.AddComment("4 extra padding bytes for GDB");
> Asm->EmitInt8(0);
> Asm->EmitInt8(0);
> Asm->EmitInt8(0);
> Asm->EmitInt8(0);
> Asm->OutStreamer.EmitLabel(Asm->Ge...
2011 Mar 30
0
[LLVMdev] More DWARF problems
...RM_ref4, VariableDIE);
Here VariableSpecDIE is referring VariableDIE, but VariableDIE is missing from the output. There are other uses of DW_FORM_ref4 also. So check in our dwarfdump output what is 0x00000883 and set appropriate breakpoint in debugger and see why it is not reaching to DwarfDebug::emitDIE().
-
Devang
> 0x000009a9: DIE attribute 0x000009ae: AT_type/FORM_ref4 has a value 0x000001c2 that is not in the current compile unit in the .debug_info section.
> 0x00000b85: DIE attribute 0x00000b8a: AT_type/FORM_ref4 has a value 0x0000055c that is not in the current compile uni...
2011 Apr 03
2
[LLVMdev] More DWARF problems
...gt;
> Here VariableSpecDIE is referring VariableDIE, but VariableDIE is missing
> from the output. There are other uses of DW_FORM_ref4 also. So check in our
> dwarfdump output what is 0x00000883 and set appropriate breakpoint in
> debugger and see why it is not reaching to DwarfDebug::emitDIE().
>
OK I've been checking this out some more, and the DIEs don't look valid to
me. Take a look at this output from dwarfdump -v:
0x000000c7: TAG_subprogram [3]
0x000000c8: AT_name( .debug_str[0x000001bd] = "construct" )
0x000000cc: AT_MIPS_linkage_name( .debug_...
2011 Mar 30
5
[LLVMdev] More DWARF problems
I've been trying to track down the problem with the DWARF info that is being
emitted by my front end, which has been broken for about a month now. Here's
what happens when I attempt to use gdb to debug one of my programs on OS X:
gdb stack crawl at point of internal error:
[ 0 ] /usr/libexec/gdb/gdb-i386-apple-darwin (align_down+0x0) [0x122300]
[ 1 ] /usr/libexec/gdb/gdb-i386-apple-darwin
2011 Apr 07
0
[LLVMdev] More DWARF problems
...e VariableSpecDIE is referring VariableDIE, but VariableDIE is missing
>> from the output. There are other uses of DW_FORM_ref4 also. So check in our
>> dwarfdump output what is 0x00000883 and set appropriate breakpoint in
>> debugger and see why it is not reaching to DwarfDebug::emitDIE().
>>
>
> OK I've been checking this out some more, and the DIEs don't look valid to
> me. Take a look at this output from dwarfdump -v:
>
> 0x000000c7: TAG_subprogram [3]
> 0x000000c8: AT_name( .debug_str[0x000001bd] = "construct" )
> 0x000000c...
2011 Mar 31
2
[LLVMdev] More DWARF problems
...gt;
> Here VariableSpecDIE is referring VariableDIE, but VariableDIE is missing
> from the output. There are other uses of DW_FORM_ref4 also. So check in our
> dwarfdump output what is 0x00000883 and set appropriate breakpoint in
> debugger and see why it is not reaching to DwarfDebug::emitDIE().
>
> OK I'm still trying to track this one down, it is apparently unrelated to
the earlier problem. After fixing the problem with the subroutine context
mentioned above, I now see the following in gdb:
Die: DW_TAG_formal_parameter (abbrev = 27, offset = 14760)
has children: FALSE
attri...