search for: dw_at_encoding

...c+ld toolchain. Target triple: 'i686-w64-mingw32'. Looking this offset (1849950870 == 0x6e440296) in dwarfdump output of the dll gave the following: 0x00000296: DW_TAG_base_type [10] DW_AT_name [DW_FORM_strp] ( .debug_str[0x0000068f] = "void") DW_AT_encoding [DW_FORM_data1] (0x00) DW_AT_byte_size [DW_FORM_data1] (0x00) .... 0x00000cf8: DW_TAG_subprogram [16] * DW_AT_low_pc [DW_FORM_addr] (0x000000006e384c30) DW_AT_high_pc [DW_FORM_data4] (0x000002b4) DW_AT_frame_base [DW_FORM...

...1 /home/yuri/test.c DW_AT_decl_line 4 DW_AT_type <144> DW_AT_location DW_OP_fbreg 0 <1>< 134> DW_TAG_base_type DW_AT_name int DW_AT_encoding DW_ATE_signed DW_AT_byte_size 4 <1>< 141> DW_TAG_base_type DW_AT_byte_size 4 DW_AT_encoding DW_ATE_signed <1>< 144> DW_TAG_array_type DW_AT_type...

...1 /home/yuri/test.c DW_AT_decl_line 4 DW_AT_type <144> DW_AT_location DW_OP_fbreg 0 <1>< 134> DW_TAG_base_type DW_AT_name int DW_AT_encoding DW_ATE_signed DW_AT_byte_size 4 <1>< 141> DW_TAG_base_type DW_AT_byte_size 4 DW_AT_encoding DW_ATE_signed <1>< 144> DW_TAG_array_type DW_AT_type...

...> .byte 2 # DW_AT_location > .byte 145 > .byte 8 > .byte 0 # End Of Children Mark > .byte 5 # Abbrev [5] 0x7f:0x7 DW_TAG_base_type > .int Linfo_string4 # DW_AT_name > .byte 5 # DW_AT_encoding > .byte 4 # DW_AT_byte_size > .byte 5 # Abbrev [5] 0x86:0x7 DW_TAG_base_type > .int Linfo_string7 # DW_AT_name > .byte 6 # DW_AT_encoding > .byte 1 # DW_AT_byte_size > .byte 6...

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

...hin a unit are relative to that unit. Should we emit unit-relative offsets instead? I've prototyped this and end up with output something like this: 0x00000051: DW_TAG_base_type [24] DW_AT_name [DW_FORM_strp] ( .debug_str[0x00000051] = "int") DW_AT_encoding [DW_FORM_data1] (0x05) DW_AT_byte_size [DW_FORM_data1] (0x04) 0x00000058: NULL 0x000001ec: Compile Unit: length = 0x0000002b version = 0x0004 abbr_offset = 0x0000 addr_size = 0x08 (next unit at 0x0000021b) 0x0000000b: DW_TAG_type_unit [25] * DW_AT_language [DW_FOR...

..._AT_entry_pc .long .Lsection_line # DW_AT_stmt_list .ascii "/home/marco/clang_issue" # DW_AT_comp_dir .byte 0 .byte 2 # Abbrev [2] 0x5c:0x7 DW_TAG_base_type .ascii "int" # DW_AT_name .byte 0 .byte 5 # DW_AT_encoding .byte 4 # DW_AT_byte_size .byte 3 # Abbrev [3] 0x63:0x18 DW_TAG_variable .ascii "something" # DW_AT_name .byte 0 .long 92 # DW_AT_type .byte 1 # DW_AT_external .byte 1...

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

...;main"); SubprogramDie.addAttribute(DW_AT_low_pc, DW_FORM_addr, 0x1000U); SubprogramDie.addAttribute(DW_AT_high_pc, DW_FORM_addr, 0x2000U); DwarfGenDIE IntDie = CUDie.addChild(DW_TAG_base_type); IntDie.addAttribute(DW_AT_name, DW_FORM_strp, "int"); IntDie.addAttribute(DW_AT_encoding, DW_FORM_data1, DW_ATE_signed); IntDie.addAttribute(DW_AT_byte_size, DW_FORM_data1, 4); DwarfGenDIE ArgcDie = SubprogramDie.addChild(DW_TAG_formal_parameter); ArgcDie.addAttribute(DW_AT_name, DW_FORM_strp, "argc"); //ArgcDie.addAttribute(DW_AT_type, DW_FORM_ref_addr, IntDie);...

...> > .byte 8 > > .byte 0 # End Of Children Mark > > .byte 5 # Abbrev [5] 0x7f:0x7 > DW_TAG_base_type > > .int Linfo_string4 # DW_AT_name > > .byte 5 # DW_AT_encoding > > .byte 4 # DW_AT_byte_size > > .byte 5 # Abbrev [5] 0x86:0x7 > DW_TAG_base_type > > .int Linfo_string7 # DW_AT_name > > .byte 6 # DW_AT_encoding > >...

...amDie.addAttribute(DW_AT_low_pc, DW_FORM_addr, 0x1000U); > SubprogramDie.addAttribute(DW_AT_high_pc, DW_FORM_addr, 0x2000U); > > DwarfGenDIE IntDie = CUDie.addChild(DW_TAG_base_type); > IntDie.addAttribute(DW_AT_name, DW_FORM_strp, "int"); > IntDie.addAttribute(DW_AT_encoding, DW_FORM_data1, DW_ATE_signed); > IntDie.addAttribute(DW_AT_byte_size, DW_FORM_data1, 4); > > DwarfGenDIE ArgcDie = SubprogramDie.addChild(DW_TAG_formal_parameter); > ArgcDie.addAttribute(DW_AT_name, DW_FORM_strp, "argc"); > //ArgcDie.addAttribute(DW_AT_type, D...

This isn't a realistic/viable implementation, just a hacked up "can I make it produce the right output" kind of thing, but while I hammer out a few more details (like fixing MC to allow multiple sections with the same name but different comdat groups) I figured I'd throw it out there to have a bit of a chat about it. I've tested simple cases of a single type and they seem to

...FORM_addr, 0x1000U); >>> SubprogramDie.addAttribute(DW_AT_high_pc, DW_FORM_addr, 0x2000U); >>> >>> DwarfGenDIE IntDie = CUDie.addChild(DW_TAG_base_type); >>> IntDie.addAttribute(DW_AT_name, DW_FORM_strp, "int"); >>> IntDie.addAttribute(DW_AT_encoding, DW_FORM_data1, DW_ATE_signed); >>> IntDie.addAttribute(DW_AT_byte_size, DW_FORM_data1, 4); >>> >>> DwarfGenDIE ArgcDie = >> SubprogramDie.addChild(DW_TAG_formal_parameter); >>> ArgcDie.addAttribute(DW_AT_name, DW_FORM_strp, "argc"); >&g...

...; >>> SubprogramDie.addAttribute(DW_AT_high_pc, DW_FORM_addr, 0x2000U); > >>> > >>> DwarfGenDIE IntDie = CUDie.addChild(DW_TAG_base_type); > >>> IntDie.addAttribute(DW_AT_name, DW_FORM_strp, "int"); > >>> IntDie.addAttribute(DW_AT_encoding, DW_FORM_data1, DW_ATE_signed); > >>> IntDie.addAttribute(DW_AT_byte_size, DW_FORM_data1, 4); > >>> > >>> DwarfGenDIE ArgcDie = > >> SubprogramDie.addChild(DW_TAG_formal_parameter); > >>> ArgcDie.addAttribute(DW_AT_name, DW_FORM_strp, &...