Displaying 20 results from an estimated 59 matches for "dw_at_decl_lin".
Did you mean:
dw_at_decl_line
2016 Mar 23
1
Clang/LLVM producing incomplete & erroneous debug information
...80
<b0> DW_AT_high_pc : 0xc9
<b4> Unknown AT value: 3fe7: 1
<b4> DW_AT_frame_base : 1 byte block: 57 (DW_OP_reg7 (rsp))
<b6> DW_AT_name : (indirect string, offset: 0xaf): main
<ba> DW_AT_decl_file : 1
<bb> DW_AT_decl_line : 16
<bc> DW_AT_prototyped : 1
<bc> DW_AT_type : <0x3f>
<c0> DW_AT_external : 1
<c0> Unknown AT value: 3fe1: 1
<2><c0>: Abbrev Number: 8 (DW_TAG_formal_parameter)
<c1> DW_AT_location : 0x23 (location...
2014 Feb 19
2
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
...line # DW_AT_stmt_list
> .int Linfo_string2 # DW_AT_comp_dir
> .byte 2 # Abbrev [2] 0x22:0x5d DW_TAG_subprogram
> .int Linfo_string3 # DW_AT_name
> .byte 1 # DW_AT_decl_file
> .byte 2 # DW_AT_decl_line
> # DW_AT_prototyped
> .int 127 # DW_AT_type
> # DW_AT_external
> .int Lfunc_begin0 # DW_AT_low_pc
> .int Lfunc_end0 # DW_AT_high_pc
> .byte 2...
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
2012 Mar 20
0
[LLVMdev] Runtime linker issue wtih X11R6 on i386 with -O3 optimization
...# 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 # DW_AT_decl_file
.byte 6 # DW_AT_decl_line
.byte 5 # DW_AT_location
.byte 3
.long something
.byte 3 # Abbrev [3] 0x7b:0x1d DW_TAG_variable
.ascii "something_else" # DW_AT_name
.byte 0
.long 92 # DW_AT_type
.byte 1 # DW_AT_externa...
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
2010 Nov 07
3
[LLVMdev] Next round of DWARF issues/questions
...of the object is zero:
<1>< 2233> DW_TAG_class_type
DW_AT_sibling <2295>
DW_AT_name tart.core.Object
* DW_AT_byte_size 0*
DW_AT_decl_file 65
DW_AT_decl_line 9
<2>< 2258> DW_TAG_member
DW_AT_name __tib
DW_AT_type <2228>
DW_AT_decl_file 65
DW_AT_decl_line 10
DW_AT_data_member_locatio...
2012 Feb 24
1
[LLVMdev] DW_AT_inline not present in assembly for an inlined inline function
...led assembly output?
I am aware that Clang uses C99 mode by default.
In case of GCC,
.uleb128 0x2 @ (DIE (0x25) DW_TAG_subprogram)
.byte 0x1 @ DW_AT_external
.ascii "t\0" @ DW_AT_name
.byte 0x1 @ DW_AT_decl_file (test.h)
.byte 0x1 @ DW_AT_decl_line
.4byte 0x30 @ DW_AT_type
.byte 0x3 @ DW_AT_inline
In case of Clang,
.byte 4 @ Abbrev [4] 0x87:0xa DW_TAG_subprogram
.byte 116 @ DW_AT_name
.byte 0
.byte 2 @ DW_AT_decl_file...
2010 Nov 08
0
[LLVMdev] Next round of DWARF issues/questions
...; <1>< 2233> DW_TAG_class_type
> DW_AT_sibling <2295>
> DW_AT_name tart.core.Object
> DW_AT_byte_size 0
> DW_AT_decl_file 65
> DW_AT_decl_line 9
> <2>< 2258> DW_TAG_member
> DW_AT_name __tib
> DW_AT_type <2228>
> DW_AT_decl_file 65
> DW_AT_decl_line 10
>...
2010 Nov 09
2
[LLVMdev] Next round of DWARF issues/questions
...<1>< 2233> DW_TAG_class_type
> DW_AT_sibling <2295>
> DW_AT_name tart.core.Object
> * DW_AT_byte_size 0*
> DW_AT_decl_file 65
> DW_AT_decl_line 9
> <2>< 2258> DW_TAG_member
> DW_AT_name __tib
> DW_AT_type <2228>
> DW_AT_decl_file 65
> DW_AT_decl_line 10
>...
2010 Nov 09
0
[LLVMdev] Next round of DWARF issues/questions
...> DW_TAG_class_type
>> DW_AT_sibling <2295>
>> DW_AT_name tart.core.Object
>> DW_AT_byte_size 0
>> DW_AT_decl_file 65
>> DW_AT_decl_line 9
>> <2>< 2258> DW_TAG_member
>> DW_AT_name __tib
>> DW_AT_type <2228>
>> DW_AT_decl_file 65
>> DW_AT_decl_line...
2019 Dec 10
2
aarch64 do not generate debug info for tls var
...(){
mtls++;
}
it emits this debug info for mtls
0x0000002a: DW_TAG_variable
DW_AT_name ("mtls")
DW_AT_type (0x00000035 "int")
DW_AT_external (true)
DW_AT_decl_file ("test.c")
DW_AT_decl_line (1)
which does not contain DW_AT_Location.
Currently, aarch64 does not emit DW_AT_Location for TLS variables.
I could see at this line, it says some restriction in aarch64 elf abi.
https://github.com/llvm-mirror/llvm/blob/master/lib/Target/AArch64/AArch64TargetObjectFile.cpp#L24
I would like to...
2018 Apr 05
1
print signature of function from dwarf info in file?
Hi
I'm using llvm-5. Browsing the source of llvm-dwarfdump and trying it on
some shared libraries, I see I can print the debug info (assuming it
exists). For some function, I'm wondering if there's a short cut to
prettyprinting the signature of a function in the library? I think, looking
at the output, that enough information exists but it seems to involve
looking at the subprogram
2014 Feb 20
2
[LLVMdev] [lldb-dev] How is variable info retrieved in debugging for executables generated by llvm backend?
...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 in the parent DIE:
>
> 0x00000022: DW_TAG_subprogram [2] *
>...
2010 Nov 26
3
[LLVMdev] Next round of DWARF issues/questions
...t; DW_TAG_class_type
>> DW_AT_sibling <2295>
>> DW_AT_name tart.core.Object
>> * DW_AT_byte_size 0*
>> DW_AT_decl_file 65
>> DW_AT_decl_line 9
>> <2>< 2258> DW_TAG_member
>> DW_AT_name __tib
>> DW_AT_type <2228>
>> DW_AT_decl_file 65
>> DW_AT_decl_line...
2020 Apr 15
2
Seeking clarification and way forward on limited scope variables.
...000000002016d1)
DW_AT_high_pc (0x000000000020170b)
0x0000007a: DW_TAG_variable
DW_AT_location (DW_OP_fbreg -24)
DW_AT_name ("Local")
DW_AT_decl_file ("MainScope.c")
DW_AT_decl_line (7)
DW_AT_type (0x0000008a "int")
----------------------------------------------
The DWARF specification provides the DW_AT_start_scope attribute to deal
with this issue (Sec 3.9 Declarations with Reduced Scope DWARFv5). This
attribute aims at limiting the sc...
2016 May 07
2
Debug info scope of explicit casting type does not seem correct
...type [DW_FORM_ref4] (cu + 0x0040 => {0x00000040})
DW_AT_name [DW_FORM_strp] ( .debug_str[0x00000060] = "T")
DW_AT_decl_file [DW_FORM_data1] ("c:\temp\ICL\LB\retain.cpp")
DW_AT_decl_line [DW_FORM_data1] (16)
Regards,
Amjad
From: David Blaikie [mailto:dblaikie at gmail.com]
Sent: Saturday, April 30, 2016 17:59
To: Aboud, Amjad <amjad.aboud at intel.com>
Cc: Adrian Prantl <aprantl at apple.com>; llvm-dev <llvm-dev at lists.llvm.org>; Clang Dev <cfe-dev a...
2019 Dec 10
2
aarch64 do not generate debug info for tls var
...> 0x0000002a: DW_TAG_variable
>> DW_AT_name ("mtls")
>> DW_AT_type (0x00000035 "int")
>> DW_AT_external (true)
>> DW_AT_decl_file ("test.c")
>> DW_AT_decl_line (1)
>>
>> which does not contain DW_AT_Location.
>>
>> Currently, aarch64 does not emit DW_AT_Location for TLS variables.
>> I could see at this line, it says some restriction in aarch64 elf abi.
>>
>> https://github.com/llvm-mirror/llvm/blob/master/lib/Ta...
2016 Apr 30
2
Debug info scope of explicit casting type does not seem correct
...type [DW_FORM_ref4] (cu + 0x0040 => {0x00000040})
DW_AT_name [DW_FORM_strp] ( .debug_str[0x00000060] = "T")
DW_AT_decl_file [DW_FORM_data1] ("c:\temp\ICL\LB\retain.cpp")
DW_AT_decl_line [DW_FORM_data1] (16)
0x00000037: NULL
command line:
clang -cc1 -triple i386-apple-ios9.0.0 -emit-obj -debug-info-kind=limited -O2 test.cpp -o - | llvm-dwarfdump -debug-dump=info -
> cat test.cpp
class A {
public:
int x;
};
class B {
public:
typedef A type;
};
template<ty...
2020 Jan 01
2
DW_OP_implicit_pointer design/implementation in general
...; -----------------------------------------------
>> 0x00000076: DW_TAG_variable
>> DW_AT_const_value (4)
>> DW_AT_name ("var")
>> DW_AT_decl_file ("ref.cc")
>> DW_AT_decl_line (9)
>> DW_AT_type (0x00000037 "int")
>>
>> 0x0000007f: DW_TAG_variable
>> DW_AT_location (indexed (0x1) loclist =
>> 0x00000023:
>> [0x0000000000400490, 0x00000000004004a0):
&...
2018 Nov 26
2
Source locations missing when using xray-account
...(0x00000000004207c8)
DW_AT_high_pc (0x0000000000420817)
DW_AT_frame_base (DW_OP_reg7 RSP)
DW_AT_linkage_name ("fqux")
DW_AT_name ("fqux")
DW_AT_decl_file ("TODO/llvm.hs")
DW_AT_decl_line (8)
DW_AT_external (true)
I suspect this is a problem with the DWARF information as when I try
to use `llvm-symboliser` with address 0x00000000004207c8 as retrieved
from the above paste, the source location is also not reported.
So, can anyone give me some practical advice about...