Displaying 4 results from an estimated 4 matches for "getlineinfoforcod".
Did you mean:
getlineinfoforcode
2012 May 06
2
[LLVMdev] DebugInfo library
...ng interface along the lines of:
> >
> > class DILineInfo {
> > const char *Name;
> > const char *FileName;
> > uint32_t Line;
> > uint32_t Column;
> > ...
> > };
> >
> > class DIContext {
> > ...
> > virtual bool getLineInfoForCode(uint64_t pc, SmallVector<DILineInfo>
> *res) = 0;
> > virtual bool getLineInfoForData(uint64_t address, DILineInfo *res) = 0;
> > };
> >
> > Any comments/suggestions?
> >
>
>
> The public DebugInfo interface was designed around a very specific use...
2012 May 05
0
[LLVMdev] DebugInfo library
...e explicit failure indicator.
>
> I see the resulting interface along the lines of:
>
> class DILineInfo {
> const char *Name;
> const char *FileName;
> uint32_t Line;
> uint32_t Column;
> ...
> };
>
> class DIContext {
> ...
> virtual bool getLineInfoForCode(uint64_t pc, SmallVector<DILineInfo> *res) = 0;
> virtual bool getLineInfoForData(uint64_t address, DILineInfo *res) = 0;
> };
>
> Any comments/suggestions?
>
The public DebugInfo interface was designed around a very specific use case, extracting file/line/column triples...
2012 May 05
2
[LLVMdev] DebugInfo library
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
2012 May 06
0
[LLVMdev] DebugInfo library
...ng interface along the lines of:
> >
> > class DILineInfo {
> > const char *Name;
> > const char *FileName;
> > uint32_t Line;
> > uint32_t Column;
> > ...
> > };
> >
> > class DIContext {
> > ...
> > virtual bool getLineInfoForCode(uint64_t pc, SmallVector<DILineInfo> *res) = 0;
> > virtual bool getLineInfoForData(uint64_t address, DILineInfo *res) = 0;
> > };
> >
> > Any comments/suggestions?
> >
>
>
> The public DebugInfo interface was designed around a very specific use cas...