search for: lsection_lin

Hi Devang, Thanks for working on that. Unfortunately after your change it still doesn't work (I've tried x86 and our backend under Linux). The problem is that you put difference between two labels .Lset7 = .Lsection_line_begin-.Lsection_line ## DW_AT_stmt_list and that will be evaluated by assembler to a constant. It has to be a label, not a constant, because it is the linker who knows the correct offset. Artur On Tue, Jun 29, 2010 at 10:18 PM, Devang Patel <devang.patel at gmail.com>wrote: > I update...

...gmail.com> wrote: > Hi Devang, > Thanks for working on that. Unfortunately after your change it still doesn't > work (I've tried x86 and our backend under Linux). What errors exactly you are seeing ? > The problem is that you put difference between two labels > .Lset7 = .Lsection_line_begin-.Lsection_line ## DW_AT_stmt_list > and that will be evaluated by assembler to a constant. It has to be a label, > not a constant, because it is the linker who knows the correct offset. How will linker translate a label into correct offset ? - Devang

I updated DwarfDebug to use section offset, instead of hard coding 0, to handle LTO properly. r107202. Thanks for brining this up. - Devang On Tue, Jun 29, 2010 at 11:27 AM, Devang Patel <devang.patel at gmail.com> wrote: > DW_AT_stmt_list attribute's value is a section offset to the line no > info for current compilation unit. If there is only one  compilation > unit

...ebug_info,"", at progbits > Lsection_info: > .section .debug_abbrev,"", at progbits > Lsection_abbrev: > .section .debug_aranges,"", at progbits > .section .debug_macinfo,"", at progbits > .section .debug_line,"", at progbits > Lsection_line: > .section .debug_loc,"", at progbits > .section .debug_pubtypes,"", at progbits > .section .debug_str,"MS", at progbits,1 > Linfo_string: > .section .debug_ranges,"", at progbits > Ldebug_range: > .section .debug_loc,"", at...

..._issue/a.c" .section .debug_info,"", at progbits .Lsection_info: .section .debug_abbrev,"", at progbits .Lsection_abbrev: .section .debug_aranges,"", at progbits .section .debug_macinfo,"", at progbits .section .debug_line,"", at progbits .Lsection_line: .section .debug_loc,"", at progbits .section .debug_pubnames,"", at progbits .section .debug_pubtypes,"", at progbits .section .debug_str,"", at progbits .Lsection_str: .section .debug_ranges,"", at progbits .Ldebug_range: .section .debug_lo...

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

On 30 Jun 2010, at 18:40, Devang Patel wrote: > On Wed, Jun 30, 2010 at 1:57 AM, Artur Pietrek <pietreka at gmail.com> > wrote: >> The problem is that you put difference between two labels >> .Lset7 = .Lsection_line_begin-.Lsection_line ## DW_AT_stmt_list >> and that will be evaluated by assembler to a constant. It has to be >> a label, >> not a constant, because it is the linker who knows the correct >> offset. > > How will linker translate a label into correct offset ? Sor...

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

....debug_abbrev,"", at progbits > > Lsection_abbrev: > > .section .debug_aranges,"", at progbits > > .section .debug_macinfo,"", at progbits > > .section .debug_line,"", at progbits > > Lsection_line: > > .section .debug_loc,"", at progbits > > .section .debug_pubtypes,"", at progbits > > .section .debug_str,"MS", at progbits,1 > > Linfo_string: > > .section .debug_ranges,"&quot...