Displaying 5 results from an estimated 5 matches for "getcompileunitforaddress".
2016 Feb 21
2
Implementation of DWARF expression parser
...ed DIE via the extractImpl() path. It’s not obvious to me why the extractImpl() code exists alongside DWARFDebugInfoEntryMinimal::extractFast(). In general, the "extract" paradigm is difficult to get a handle on, and I’ve yet to find any documentation. Another example is the DWARFContext::getCompileUnitForAddress() API, which is private; I’ve couldn't find a way to invoke its logic (aside from iterating all the units and using DWARFDebugInfoEntryMinimal::getInlinedChainForAddress() on each). I have the sensation that I’m misunderstanding the intended usage pattern for these objects entirely, or that at...
2014 Aug 13
2
[LLVMdev] Advice for setting debug locations
...ges at
/Users/kfischer/Documents/julia-debug/deps/llvm-svn/lib/DebugInfo/DWARFUnit.cpp:302
generate at /Users/kfischer/Documents/julia-debug/deps/llvm-svn/lib/DebugInfo/DWARFDebugAranges.cpp:54
getDebugAranges at
/Users/kfischer/Documents/julia-debug/deps/llvm-svn/lib/DebugInfo/DWARFContext.cpp:270
getCompileUnitForAddress at
/Users/kfischer/Documents/julia-debug/deps/llvm-svn/lib/DebugInfo/DWARFContext.cpp:423
Can somebody tell me what the correct way to achieve this is?
[1] https://github.com/JuliaLang/julia/commit/e494cb6dff193ecb0e254981be0f1122ae294d04
2014 Aug 13
2
[LLVMdev] Advice for setting debug locations
...ia-debug/deps/llvm-svn/lib/DebugInfo/DWARFUnit.cpp:302
>> generate at /Users/kfischer/Documents/julia-debug/deps/llvm-svn/lib/DebugInfo/DWARFDebugAranges.cpp:54
>> getDebugAranges at
>> /Users/kfischer/Documents/julia-debug/deps/llvm-svn/lib/DebugInfo/DWARFContext.cpp:270
>> getCompileUnitForAddress at
>> /Users/kfischer/Documents/julia-debug/deps/llvm-svn/lib/DebugInfo/DWARFContext.cpp:423
>>
>> Can somebody tell me what the correct way to achieve this is?
>>
>> [1] https://github.com/JuliaLang/julia/commit/e494cb6dff193ecb0e254981be0f1122ae294d04
>> ______...
2016 Jul 10
2
Implementation of DWARF expression parser
...any documentation.
>
> The DIE extraction is handled only by extractFast. DWARFUnit::extract[Impl]() is only about the Unit header parsing AFAICS. The DIEs are read lazily by the first method that requests them (see extractDIEsifNeeded()).
>
>> Another example is the DWARFContext::getCompileUnitForAddress() API, which is private; I’ve couldn't find a way to invoke its logic (aside from iterating all the units and using DWARFDebugInfoEntryMinimal::getInlinedChainForAddress() on each).
>
> getCompileUnitForAddress() is only used as a helper for the high-level line-tables abstraction. It’s n...
2014 Aug 13
2
[LLVMdev] Advice for setting debug locations
...Info/DWARFUnit.cpp:302
>>>> generate at /Users/kfischer/Documents/julia-debug/deps/llvm-svn/lib/DebugInfo/DWARFDebugAranges.cpp:54
>>>> getDebugAranges at
>>>> /Users/kfischer/Documents/julia-debug/deps/llvm-svn/lib/DebugInfo/DWARFContext.cpp:270
>>>> getCompileUnitForAddress at
>>>> /Users/kfischer/Documents/julia-debug/deps/llvm-svn/lib/DebugInfo/DWARFContext.cpp:423
>>>>
>>>> Can somebody tell me what the correct way to achieve this is?
>>>>
>>>> [1] https://github.com/JuliaLang/julia/commit/e494cb6dff193ecb...