search for: debug_info_begin0

....cfi_sections .debug_frame .bss .L.bss_end: ... .L.debug_abbrev_end: .section .debug_aranges,"", at progbits .long 36 # Length of ARange Set .short 2 # DWARF Arange version number .long .L.debug_info_begin0 # Offset Into Debug Info Section .byte 4 # Address Size (in bytes) .byte 0 # Segment Size (in bytes) .byte 255 .byte 255 .byte 255 .byte 255 .long comm .Lset0 = .L.bss_end-com...

...000000000000000 T foo I would like to know what "$tmp0" is. Furthermore, if I pass -g to clang, I see a whole bunch of such symbols. Some of them appear to be MIPS specific DWARF extensions. But the ones I'm not able to figure out are the $tmp* symbols: # nm a.o 0000000000000000 N $.debug_info_begin0 0000000000000000 N $debug_cmdline 0000000000000020 t $debug_end0 0000000000000000 N $debug_range 0000000000000000 t $func_begin0 0000000000000020 t $func_end0 0000000000000000 N $info_string 0000000000000000 N $info_string0 00000000000000a7 N $info_string1 00000000000000ab N $info_string2 000000000...

....bss > .L.bss_end: > ... > .L.debug_abbrev_end: > .section .debug_aranges,"", at progbits > .long 36 # Length of ARange Set > .short 2 # DWARF Arange version number > .long .L.debug_info_begin0 # Offset Into Debug Info Section > .byte 4 # Address Size (in bytes) > .byte 0 # Segment Size (in bytes) > .byte 255 > .byte 255 > .byte 255 > .byte 255 > .long...

....bss > .L.bss_end: > ... > .L.debug_abbrev_end: > .section .debug_aranges,"", at progbits > .long 36 # Length of ARange Set > .short 2 # DWARF Arange version number > .long .L.debug_info_begin0 # Offset Into Debug Info Section > .byte 4 # Address Size (in bytes) > .byte 0 # Segment Size (in bytes) > .byte 255 > .byte 255 > .byte 255 > .byte 255 > .long...

...ct/debug this? Do we have tests that check that -gsplit-dwarf succeeds (i.e. compile and link step work)? $ cat a.cc int foo(int x) { return x + 1; } int main() { return foo(42); } $ ./bin/clang++ -gsplit-dwarf a.cc /tmp/a-005b1a.o(.debug_pubnames+0x6): error: undefined reference to '.L.debug_info_begin0' clang-3.3: error: linker command failed with exit code 1 (use -v to see invocation) $ ./bin/clang++ -gsplit-dwarf a.cc -### clang version 3.4 (189088) Target: x86_64-unknown-linux-gnu Thread model: posix "/llvm_build_clang/bin/clang-3.3" "-cc1" "-triple" "...

...+ -40] = R1;; > SP = FP;; > J30 = [SP + -8];; > FP = [SP + -4];; > jump J30;; > Ltmp0: > Ltmp1: > .size main, Ltmp1-main > Lfunc_end0: > > Ltext_end: > .data > Ldata_end: > .text > Lsection_end1: > .section .debug_info,"", at progbits > L.debug_info_begin0: > .int 148 # Length of Compilation Unit Info > .short 2 # DWARF version number > .int L.debug_abbrev_begin # Offset Into Abbrev. Section > .byte 4 # Address Size (in bytes) > .byte 1 # Abbrev...

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

...> > Ltmp0: > > Ltmp1: > > .size main, Ltmp1-main > > Lfunc_end0: > > > > Ltext_end: > > .data > > Ldata_end: > > .text > > Lsection_end1: > > .section .debug_info,"", at progbits > > L.debug_info_begin0: > > .int 148 # Length of Compilation Unit Info > > .short 2 # DWARF version number > > .int L.debug_abbrev_begin # Offset Into Abbrev. Section > > .byte 4 # Address Size (in...