Displaying 6 results from an estimated 6 matches for "yangyy".
2014 Feb 19
2
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
...t; Linfo_string0:
> .asciz "clang version 3.3 (/opt/git.repo/clang.git/
> b422d20530588813b09057b45d5b383f0b175ced) (/opt/git.repo/llvm.git/
> 57b428f0a6be7b81bc364b0088992b1f820b516e)"
> Linfo_string1:
> .asciz "test.c"
> Linfo_string2:
> .asciz "/home/yangyy/workspace/newlib"
> Linfo_string3:
> .asciz "main"
> Linfo_string4:
> .asciz "int"
> Linfo_string5:
> .asciz "argc"
> Linfo_string6:
> .asciz "argv"
> Linfo_string7:
> .asciz "char"
> Linfo_string8:
> .asciz...
2012 Jul 03
4
[LLVMdev] target hexagon and sparcv9 lead to llc crack
...align 4
%cmp = icmp sgt i32 %0, %1
%cond = select i1 %cmp, i32 1, i32 0
ret i32 %cond
}
(3) llc -march=sparcv9 test.ll -o test.s
ExpandIntegerResult #0: 0xaf38960: i64 = FrameIndex<1> [ORD=2] [ID=0]
Do not know how to expand the result of this operator!
UNREACHABLE executed at
/home/yangyy/git.repo/llvm.git/lib/CodeGen/SelectionDAG/LegalizeIntegerTypes.cpp:1089!
0 llc 0x08c2512b
Stack dump:
0. Program arguments: llc -march=sparcv9 test.ll -o test.s
1. Running pass 'Function Pass Manager' on module 'test.ll'.
2. Running pass 'SPARC DAG->DAG Pattern Instruction...
2012 Jul 03
0
[LLVMdev] target hexagon and sparcv9 lead to llc crack
...select i1 %cmp, i32 1, i32 0
> ret i32 %cond
> }
>
> (3) llc -march=sparcv9 test.ll -o test.s
>
> ExpandIntegerResult #0: 0xaf38960: i64 = FrameIndex<1> [ORD=2] [ID=0]
>
> Do not know how to expand the result of this operator!
> UNREACHABLE executed at
> /home/yangyy/git.repo/llvm.git/lib/CodeGen/SelectionDAG/LegalizeIntegerTypes.cpp:1089!
> 0 llc 0x08c2512b
> Stack dump:
> 0. Program arguments: llc -march=sparcv9 test.ll -o test.s
> 1. Running pass 'Function Pass Manager' on module 'test.ll'.
> 2. Running pass ...
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
2014 Feb 20
2
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
...isters and also tell LLDB the DWARF register number for
> each register accurately.
>
> Variable "a" has debug info:
>
> 0x00000054: DW_TAG_variable [4]
> DW_AT_name( "a" )
> DW_AT_decl_file(
> "/home/yangyy/workspace/newlib/test.c" )
> DW_AT_decl_line( 4 )
> DW_AT_type( {0x0000007f} ( int ) )
> DW_AT_location( fbreg +16 )
>
> The location says it is at the frame base register + 16 bytes. The frame
> base is defined i...