search for: lfunc_begin0

...; DWARF Arange version number .long .Lcu_begin0 ; Offset Into Debug Info Section .byte 2 ; Address Size (in bytes) .byte 0 ; Segment Size (in bytes) .short my_array .short .Lsec_end0-my_array .short .Lfunc_begin0 .short .Lsec_end1-.Lfunc_begin0 .short 0 ; ARange terminator ...but I cannot see documentation anywhere on what a consumer is expected to do with such information, and how *in general* multiple address spaces are expected to work for llvm and gcc when generating DWA...

Hi, I am trying to execute a simple hello world program compiled like so: path/to/compiled/clang -o test --target=aarch64-linux-gnu -march=armv8.5-a -fsanitize=hwaddress --sysroot=/usr/aarch64-linux-gnu/ -L/usr/lib/gcc/aarch64-linux-gnu/10.1.0/ -g test.c However, when I look at the disassembly, there is an unknown instruction listed at 0x2d51c: 000000000002d4c0 main: 2d4c0: ff c3 00 d1

...t;, at progbits > Ldebug_range: > .section .debug_loc,"", at progbits > Lsection_debug_loc: > .text > Ltext_begin: > .data > .file 1 "test.c" > .text > .global main > .type main, at function > main: # @main > Lfunc_begin0: > .loc 1 3 0 # test.c:3:0 > # BB#0: # %entry > .loc 1 2 0 prologue_end # test.c:2:0 > [SP + -4] = FP;; > [SP + -8] = J30;; > FP = SP;; > J31 = -40;; > SP = SP + J31;; > #DEBUG_VALUE: main:argc <- undef > #DEB...

...n_str: .section .debug_ranges,"", at progbits .Ldebug_range: .section .debug_loc,"", at progbits .Lsection_debug_loc: .text .Ltext_begin: .data .text .globl moo .align 16, 0x90 .type moo, at function moo: # @moo .Ltmp3: .cfi_startproc .Lfunc_begin0: .loc 1 12 0 # a.c:12:0 # BB#0: pushl %ebp .Ltmp4: .cfi_def_cfa_offset 8 .Ltmp5: .cfi_offset %ebp, -8 movl %esp, %ebp .Ltmp6: .cfi_def_cfa_register %ebp pushl %ebx subl $20, %esp .Ltmp7: .cfi_offset %ebx, -12 calll .L0$pb .L0$pb: popl %eax .Ltmp8: addl $_GLOBAL_OFFSET_T...

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

...: c <84> DW_AT_decl_file : 1 <85> DW_AT_decl_line : 5 <86> DW_AT_type : <0x8d> <8a> DW_AT_location : 1 byte block: 54 (DW_OP_reg4) ... Looking at assembly code I've got: ... foo: # @foo .Lfunc_begin0: .loc 1 6 0 .Ltmp3: # BB#0: pushl %ebp .Ltmp0: movl %esp, %ebp .Ltmp1: pushl %esi pushl %eax .Ltmp2: #DEBUG_VALUE: foo:c <- ESP+4294967295 # argpass.c:5:14 movl 8(%ebp), %esi .loc 1 7 5 .Ltmp4: movl %esi, (%esp) # argpass.c:7...

...; > Lsection_debug_loc: > > .text > > Ltext_begin: > > .data > > .file 1 "test.c" > > .text > > .global main > > .type main, at function > > main: # @main > > Lfunc_begin0: > > .loc 1 3 0 # test.c:3:0 > > # BB#0: # %entry > > .loc 1 2 0 prologue_end # test.c:2:0 > > [SP + -4] = FP;; > > [SP + -8] = J30;; > > FP = SP;; > > J31 = -4...