search for: standard_opcode_lengths

Displaying 5 results from an estimated 5 matches for "standard_opcode_lengths".

2008 Jul 17
3
[LLVMdev] RFC: debug_line Emission
...ug_line[0x00000000] ---------------------------------------------------------------------- Line table prologue: total_length: 0x00000027 version: 0x0002 prologue_length: 0x00000017 min_inst_length: 0x01 default_is_stmt: 0x01 line_base: -10 line_range: 245 opcode_base: 0x0a standard_opcode_lengths[ DW_LNS_copy ] = 0 standard_opcode_lengths[ DW_LNS_advance_pc ] = 1 standard_opcode_lengths[ DW_LNS_advance_line ] = 1 standard_opcode_lengths[ DW_LNS_set_file ] = 1 standard_opcode_lengths[ DW_LNS_set_column ] = 1 standard_opcode_lengths[ DW_LNS_negate_stmt...
2014 Feb 19
2
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
...debug_aranges contents: > > .debug_line contents: > Line table prologue: > total_length: 0x00000037 > version: 2 > prologue_length: 0x0000001d > min_inst_length: 1 > default_is_stmt: 1 > line_base: -5 > line_range: 14 > opcode_base: 13 > standard_opcode_lengths[DW_LNS_copy] = 0 > standard_opcode_lengths[DW_LNS_advance_pc] = 1 > standard_opcode_lengths[DW_LNS_advance_line] = 1 > standard_opcode_lengths[DW_LNS_set_file] = 1 > standard_opcode_lengths[DW_LNS_set_column] = 1 > standard_opcode_lengths[DW_LNS_negate_stmt] = 0 > standard_opcode_...
2014 Feb 18
1
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
All of this information is contained in the DWARF debug info that you must generate. Are you generating DWARF? If not, you will need to. If so, please attach an example program that contains DWARF and specify which function you are having trouble getting variable information for. Greg Clayton On Feb 18, 2014, at 12:44 AM, 杨勇勇 <triple.yang at gmail.com> wrote: > Hi, all > > I
2014 Feb 18
4
[LLVMdev] How is variable info retrieved in debugging for executables generated by llvm backend?
Hi, all I ported llvm backend and lldb recently. Both tools can basically work. lldb is able to debug programs in asm style and frame unwinding is OK. But "frame variable XX" does not work because lldb is not able to determine the address of XX from debug info. Can someone give any clue? Thanks in advance. -- 杨勇勇 (Yang Yong-Yong) -------------- next part -------------- An HTML
2014 Feb 20
2
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
...ents: > > Line table prologue: > > total_length: 0x00000037 > > version: 2 > > prologue_length: 0x0000001d > > min_inst_length: 1 > > default_is_stmt: 1 > > line_base: -5 > > line_range: 14 > > opcode_base: 13 > > standard_opcode_lengths[DW_LNS_copy] = 0 > > standard_opcode_lengths[DW_LNS_advance_pc] = 1 > > standard_opcode_lengths[DW_LNS_advance_line] = 1 > > standard_opcode_lengths[DW_LNS_set_file] = 1 > > standard_opcode_lengths[DW_LNS_set_column] = 1 > > standard_opcode_lengths[DW_LNS_negate_stmt]...