Displaying 5 results from an estimated 5 matches for "lexicalblock".
Did you mean:
dilexicalblock
2011 Apr 27
1
[LLVMdev] LLVM internal getDirectory() for LexicalBlock debug information returns filename?
...VMContext &Ctx = Inst->getParent()->getParent()->getContext();
DIScope Scope(Loc.getScope(Ctx));
StringRef Dir = Scope.getDirectory(); // Wrong: contains filename
iso. directory
....
}
}
Here, if Scope refers to a Subprogram, this works correctly. However,
if Scope is a LexicalBlock, getDirectory() returns the filename
(conv.c) iso. the directory. The associated .ll does have a reference
to the proper directory (/home1/martijn/hello) in !1 referred from
!33:
...
store i32 %0, i32* %px.addr.09, align 4, !dbg !33, !tbaa !36
...
!0 = metadata !{i32 589870, i32 0, metada...
2015 Nov 18
3
RFC: Supporting all entities declared in lexical scope in LLVM debug info
...here is only one concrete function with one lexical block (DW_TAG_lexical_block) entry. Each entity will have a dwarf entry placed under the lexical block scope the same as appear in the source.
(1) DW_TAG_subprogram (concrete)
DW_AT_name (= "foo")
DW_AT_low_pc
DW_AT_low_high
(2) LexicalBlock
DW_AT_low_pc
DW_AT_low_high
(3) DW_TAG_imported_module
DW_AT_import (=> N)
(3) DW_TAG_imported_declaration
DW_AT_import (=> N::D)
(3) DW_TAG_typedef
DW_AT_name (= "A")
DW_AT_type (=> int)
(3) DW_TAG_class_type
DW_AT_name (= "B")
(4) DW_TAG_variab...
2016 Jan 19
2
RFC: Supporting all entities declared in lexical scope in LLVM debug info
...lexical_block) entry. Each entity will have a dwarf entry placed
> under the lexical block scope the same as appear in the source.
>
>
>
> (1) DW_TAG_subprogram (concrete)
>
> DW_AT_name (= "foo")
>
> DW_AT_low_pc
>
> DW_AT_low_high
>
>
>
> (2) LexicalBlock
>
> DW_AT_low_pc
>
> DW_AT_low_high
>
>
>
> (3) DW_TAG_imported_module
>
> DW_AT_import (=> N)
>
>
>
> (3) DW_TAG_imported_declaration
>
> DW_AT_import (=> N::D)
>
>
>
> (3) DW_TAG_typedef
>
> DW_AT_name (= "A")
>...
2013 Oct 15
2
[LLVMdev] MCJIT and DWARF debugging info and lldb
Hey folks, I've written a Common Lisp compiler using LLVM as the
back end. I switched to MCJIT a couple of days ago. I generate DWARF
debugging information for each Compile Unit, Function, LexicalBlock and
line numbers (using DIBuilder). (I'm on OS X 10.8.5;
XCode 5.0; ToT LLVM/Clang build rev 192521)
When I check my backtraces in lldb (stock lldb from Xcode 5.0) I don't see my DWARF debugging info
as I expected - should I be? What is the status of DWARF debugging with
MCJIT?
Here'...
2013 Oct 15
0
[LLVMdev] MCJIT and DWARF debugging info and lldb
...5, 2013 10:27 AM
To: llvmdev at cs.uiuc.edu
Subject: [LLVMdev] MCJIT and DWARF debugging info and lldb
Hey folks, I've written a Common Lisp compiler using LLVM as the back end. I switched to MCJIT a couple of days ago. I generate DWARF debugging information for each Compile Unit, Function, LexicalBlock and line numbers (using DIBuilder). (I'm on OS X 10.8.5; XCode 5.0; ToT LLVM/Clang build rev 192521)
When I check my backtraces in lldb (stock lldb from Xcode 5.0) I don't see my DWARF debugging info as I expected - should I be? What is the status of DWARF debugging with MCJIT?
Here'...