search for: line_range

Hi All, Will try and keep brief, excuse the poor graphics skills, first time using GIMP. I would like to make the first one look (somewhat) like the second if possible. From: http://d.imagehost.org/0519/Screen_shot_2010-12-08_at_3_50_23_PM.png To here: http://d.imagehost.org/0293/Screen_shot_2010-12-08_at_3_50_23_PM2.png I imagine the line going over the top with the p-values is probably not

Hi all, I'm preparing to propose some additional error checks for the DWARF debug line parser which we have locally. However, there have been some valid comments in the past that some errors really shouldn't prevent parsing for certain situations. For example, a line_range of 0 would only be an issue if anything needed that information (and would consequently divide by zero), whilst the include directories and file names table should be terminated with null bytes, but the parser could use the header length field to identify when the tables have ended instead. After...

...; >> Hi all, >> >> I'm preparing to propose some additional error checks for the DWARF debug line parser which we have locally. However, there have been some valid comments in the past that some errors really shouldn't prevent parsing for certain situations. For example, a line_range of 0 would only be an issue if anything needed that information (and would consequently divide by zero), whilst the include directories and file names table should be terminated with null bytes, but the parser could use the header length field to identify when the tables have ended instead. >&gt...

...---------------------------------- debug_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 ] =...

...> .debug_frame contents: > > > .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_op...

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

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

..._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_se...