search for: variablespecdie

...DwarfDebug.cpp was preparing dwarf info, it created a DIE 0x00000592 that was referred by another DIE 0x00000883 but somehow DIE 0x00000592 was not emitted. This could be a bug in DwarfDebug.cpp or how debug info is generated by FE. In DwarfDebug.cpp, you'll see code like addDIEEntry(VariableSpecDIE, dwarf::DW_AT_specification, dwarf::DW_FORM_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...

...rf info, it > created a DIE 0x00000592 that was referred by another DIE 0x00000883 but > somehow DIE 0x00000592 was not emitted. This could be a bug in > DwarfDebug.cpp or how debug info is generated by FE. > > In DwarfDebug.cpp, you'll see code like > > addDIEEntry(VariableSpecDIE, > dwarf::DW_AT_specification, dwarf::DW_FORM_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 br...

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

...a DIE 0x00000592 that was referred by another DIE 0x00000883 but >> somehow DIE 0x00000592 was not emitted. This could be a bug in >> DwarfDebug.cpp or how debug info is generated by FE. >> >> In DwarfDebug.cpp, you'll see code like >> >> addDIEEntry(VariableSpecDIE, >> dwarf::DW_AT_specification, dwarf::DW_FORM_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 an...

...rf info, it > created a DIE 0x00000592 that was referred by another DIE 0x00000883 but > somehow DIE 0x00000592 was not emitted. This could be a bug in > DwarfDebug.cpp or how debug info is generated by FE. > > In DwarfDebug.cpp, you'll see code like > > addDIEEntry(VariableSpecDIE, > dwarf::DW_AT_specification, dwarf::DW_FORM_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 br...