search for: dw_children_yes

Displaying 7 results from an estimated 7 matches for "dw_children_yes".

2017 Feb 25
2
[DebugInfo] [DWARFv5] .debug_abbrev contents for different implicit_const values
...values we end up with only one abbrev in .debug_abbrev section. For example consider two structures: S1 with implicit_const attribute ATTR and value VAL1 and S2 with implicit_const ATTR and value VAL2. The .debug_abbrev section will contain only 1 related record: [N] DW_TAG_structure_type DW_CHILDREN_yes DW_AT_ATTR DW_FORM_implicit_const VAL1 // .... However it looks like we need to have two different abbreviations here: [N] DW_TAG_structure_type DW_CHILDREN_yes DW_AT_ATTR DW_FORM_implicit_const VAL1 // .... [M] DW_TAG_structure_type...
2014 Feb 19
2
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
...# End Of Children Mark > L.debug_info_end0: > .section .debug_abbrev,"", at progbits > L.debug_abbrev_begin: > .byte 1 # Abbreviation Code > .byte 17 # DW_TAG_compile_unit > .byte 1 # DW_CHILDREN_yes > .byte 37 # DW_AT_producer > .byte 14 # DW_FORM_strp > .byte 19 # DW_AT_language > .byte 5 # DW_FORM_data2 > .byte 3 # DW_AT_name > .byte 14 # DW_FOR...
2012 Mar 20
0
[LLVMdev] Runtime linker issue wtih X11R6 on i386 with -O3 optimization
...# End Of Children Mark .byte 0 # End Of Children Mark .Linfo_end1: .section .debug_abbrev,"", at progbits .Labbrev_begin: .byte 1 # Abbreviation Code .byte 17 # DW_TAG_compile_unit .byte 1 # DW_CHILDREN_yes .byte 37 # DW_AT_producer .byte 8 # DW_FORM_string .byte 19 # DW_AT_language .byte 5 # DW_FORM_data2 .byte 3 # DW_AT_name .byte 8 # DW_FORM_string .byte 82...
2014 Feb 18
1
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
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
2014 Feb 18
4
[LLVMdev] How is variable info retrieved in debugging for executables generated by llvm backend?
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
2020 Jun 22
3
Hardware ASan Generating Unknown Instruction
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
2014 Feb 20
2
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
...o_end0: > > .section .debug_abbrev,"", at progbits > > L.debug_abbrev_begin: > > .byte 1 # Abbreviation Code > > .byte 17 # DW_TAG_compile_unit > > .byte 1 # DW_CHILDREN_yes > > .byte 37 # DW_AT_producer > > .byte 14 # DW_FORM_strp > > .byte 19 # DW_AT_language > > .byte 5 # DW_FORM_data2 > > .byte 3...