Displaying 6 results from an estimated 6 matches for "dw_children_no".
2014 Feb 19
2
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
...ase
> .byte 10 # DW_FORM_block1
> .byte 0 # EOM(1)
> .byte 0 # EOM(2)
> .byte 3 # Abbreviation Code
> .byte 5 # DW_TAG_formal_parameter
> .byte 0 # DW_CHILDREN_no
> .byte 3 # DW_AT_name
> .byte 14 # DW_FORM_strp
> .byte 58 # DW_AT_decl_file
> .byte 11 # DW_FORM_data1
> .byte 59 # DW_AT_decl_line
> .byte 11 # DW_F...
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
2012 Mar 20
0
[LLVMdev] Runtime linker issue wtih X11R6 on i386 with -O3 optimization
...# DW_AT_comp_dir
.byte 8 # DW_FORM_string
.byte 0 # EOM(1)
.byte 0 # EOM(2)
.byte 2 # Abbreviation Code
.byte 36 # DW_TAG_base_type
.byte 0 # DW_CHILDREN_no
.byte 3 # DW_AT_name
.byte 8 # DW_FORM_string
.byte 62 # DW_AT_encoding
.byte 11 # DW_FORM_data1
.byte 11 # DW_AT_byte_size
.byte 11 # DW_FORM_data1
.byte 0...
2014 Feb 20
2
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
...gt; .byte 0 # EOM(1)
> > .byte 0 # EOM(2)
> > .byte 3 # Abbreviation Code
> > .byte 5 # DW_TAG_formal_parameter
> > .byte 0 # DW_CHILDREN_no
> > .byte 3 # DW_AT_name
> > .byte 14 # DW_FORM_strp
> > .byte 58 # DW_AT_decl_file
> > .byte 11 # DW_FORM_data1
> > .byte 59...
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