search for: mspu

...t; .asciz "char" > Linfo_string8: > .asciz "a" > Linfo_string9: > .asciz "b" > Linfo_string10: > .asciz "c" > > ######################################### > # dwarf debug info dumpped from its executable file with llvm-dwarfdump > mspu.out: file format ELF32-mspu > > .debug_abbrev contents: > Abbrev table for offset: 0x00000000 > [1] DW_TAG_compile_unit DW_CHILDREN_yes > DW_AT_producer DW_FORM_strp > DW_AT_language DW_FORM_data2 > DW_AT_name DW_FORM_strp > DW_AT_low_pc DW_FORM_addr > DW_AT_stmt_list D...

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

..."a" > > Linfo_string9: > > .asciz "b" > > Linfo_string10: > > .asciz "c" > > > > ######################################### > > # dwarf debug info dumpped from its executable file with llvm-dwarfdump > > mspu.out: file format ELF32-mspu > > > > .debug_abbrev contents: > > Abbrev table for offset: 0x00000000 > > [1] DW_TAG_compile_unit DW_CHILDREN_yes > > DW_AT_producer DW_FORM_strp > > DW_AT_language DW_FORM_data2 > > DW_AT_name...