Displaying 3 results from an estimated 3 matches for "__debug_loc".
2008 Jun 21
3
[LLVMdev] llvm-gcc -O0 compile times
...__debug_abbrev): 1535
Section (__DWARF, __debug_aranges): 48 | Section (__DWARF,
__debug_aranges): 0
Section (__DWARF, __debug_macinfo): 0 Section (__DWARF,
__debug_macinfo): 0
Section (__DWARF, __debug_line): 126106 | Section (__DWARF,
__debug_line): 149797
Section (__DWARF, __debug_loc): 0 Section (__DWARF, __debug_loc): 0
Section (__DWARF, __debug_pubnames): 168873 | Section (__DWARF,
__debug_pubnames): 165104
Section (__DWARF, __debug_pubtypes): 32449 |
Section (__DWARF, __debug_str): 17541 | Section (__DWARF,
__debug_str): 0
Section (__DWARF, __debug_ran...
2014 Jun 02
2
[LLVMdev] [lldb-dev] MCJIT Mach-O JIT debugging
....__debug_line
> 0x00000005 dwarf-str [0x00007fc4230f5a0b-0x00007fc4230f5a4b) 0x00000c0b 0x00000040 0x02000000 JIT(0x7fc4230f4e00).__DWARF.__debug_str
> 0x00000006 dwarf-loc 0x00000c4b 0x00000000 0x02000000 JIT(0x7fc4230f4e00).__DWARF.__debug_loc
> 0x00000007 dwarf-ranges 0x00000c4b 0x00000000 0x02000000 JIT(0x7fc4230f4e00).__DWARF.__debug_ranges
> 0x00000300 container [0x0000000112efce80-0x0000000112efcec0)* 0x00000c50 0x00000040 0x00000000 JIT(0x7fc4230f4e00).__LD
> 0x0000...
2014 Jun 02
2
[LLVMdev] [lldb-dev] MCJIT Mach-O JIT debugging
I didn't get to work on this more last week, but I'll look at incorporating
that suggestion.
The other question of course is how to do this in LLDB. Right, now what I'm
doing is going through and adjusting the load address of every leaf in the
section tree. That basically works and gets me backtraces with the correct
function names and the ability to set breakpoints at functions in