search for: getlineinfoforaddress

...ext.h: At global scope: /extra/xguo/workspace/llvm/include/llvm/DebugInfo/DIContext.h:52: error: 'uint64_t' has not been declared In file included from DIContext.cpp:11: /extra/xguo/workspace/llvm/include/llvm/DebugInfo/DIContext.h:52: warning: 'virtual llvm::DILineInfo llvm::DIContext::getLineInfoForAddress(int)' was hidden DWARFContext.h:69: warning: by 'virtual llvm::DILineInfo llvm::DWARFContext::getLineInfoForAddress(uint64_t)' DIContext.cpp: In static member function 'static llvm::DIContext* llvm::DIContext::getDWARFContext(bool, llvm::StringRef, llvm::StringRef, llvm::StringRef...

...l scope: > /extra/xguo/workspace/llvm/include/llvm/DebugInfo/DIContext.h:52: error: 'uint64_t' has not been declared > In file included from DIContext.cpp:11: > /extra/xguo/workspace/llvm/include/llvm/DebugInfo/DIContext.h:52: warning: 'virtual llvm::DILineInfo llvm::DIContext::getLineInfoForAddress(int)' was hidden > DWARFContext.h:69: warning:   by 'virtual llvm::DILineInfo llvm::DWARFContext::getLineInfoForAddress(uint64_t)' > DIContext.cpp: In static member function 'static llvm::DIContext* llvm::DIContext::getDWARFContext(bool, llvm::StringRef, llvm::StringRef, llvm:...

Hi, I would like to extend DebugInfo library for the purpose of using it in AddressSanitizer/ThreadSanitizer run-time libraries. Current interface is: class DILineInfo { const char *FileName; uint32_t Line; uint32_t Column; ... }; class DIContext { ... virtual DILineInfo getLineInfoForAddress(uint64_t address) = 0; }; First, I would like to get function name associated with the address. Then, I would like to get inlined frames as well. Then, I would like to be able to get the same info about global variables. Finally, I would like to receive explicit failure indicator. I see the resul...

...ime libraries. > > > > Current interface is: > > > > class DILineInfo { > > const char *FileName; > > uint32_t Line; > > uint32_t Column; > > ... > > }; > > > > class DIContext { > > ... > > virtual DILineInfo getLineInfoForAddress(uint64_t address) = 0; > > }; > > > > First, I would like to get function name associated with the address. > > Then, I would like to get inlined frames as well. > > Then, I would like to be able to get the same info about global > variables. > > Finally, I wo...

...purpose of using it in AddressSanitizer/ThreadSanitizer run-time libraries. > > Current interface is: > > class DILineInfo { > const char *FileName; > uint32_t Line; > uint32_t Column; > ... > }; > > class DIContext { > ... > virtual DILineInfo getLineInfoForAddress(uint64_t address) = 0; > }; > > First, I would like to get function name associated with the address. > Then, I would like to get inlined frames as well. > Then, I would like to be able to get the same info about global variables. > Finally, I would like to receive explicit failu...

That relocation handling is only done for the llvm-dwarfdump binary. MCJIT handles relocations a bit different. I think you just need to go ahead and allow the MCJIT relocation handling machinery to work on non-alloc sections and it should go ahead and handle these just fine, unless you're using the existing stuff in lib/DebugInfo to print out information or something? If this isn't what

...ime libraries. > > > > Current interface is: > > > > class DILineInfo { > > const char *FileName; > > uint32_t Line; > > uint32_t Column; > > ... > > }; > > > > class DIContext { > > ... > > virtual DILineInfo getLineInfoForAddress(uint64_t address) = 0; > > }; > > > > First, I would like to get function name associated with the address. > > Then, I would like to get inlined frames as well. > > Then, I would like to be able to get the same info about global variables. > > Finally, I would l...

I'm working on adding source-based profiling support for MCJIT and in the process of implementing this, I came across a test case where an object is being generated that wants to have relocations applied to the .debug_line section. I see in the DebugInfo code that it currently only supports relocations applied to either the .debug_info or the .debug_info.dwo section. Can anyone give me an

...and size from the SymbolRef interface. So far, so good, and all of this is currently happening in trunk. As a next step, I want to use the DWARF information to figure out source file and line number information for the functions. My plan is to add a new function to the DIContext interface called getLineInfoForAddressRange, which will do pretty much what the existing getLineInfoForAddress does except that it will return a vector of <address, DILineInfo> pairs for all lines in the range. It happens that the ObjectImage class aggregates an ObjectFile, so I'm going to provide a method to retrieve the und...