Displaying 5 results from an estimated 5 matches for "absolutefilepath".
2014 May 07
5
[LLVMdev] DWARF unmangled subprog name (DW_AT_name)
...ss that with the
> public API (it works nicely in gdb/lldb though).
>
Alright, I see why it makes sense. We can pass this information through
DILineInfoSpecifier. In fact, probably it makes sense to change the layout
of this structure:
there would be 3 types of file/line info (None, Regular, AbsoluteFilePath).
(though, probably we may make latter the default) and 3 types of function
name info (None, Name, LinkageName).
>
>
> On Wed, May 7, 2014 at 2:36 PM, Alexey Samsonov <samsonov at google.com>wrote:
>
>>
>> On Wed, May 7, 2014 at 11:33 AM, Eric Christopher <echrist...
2014 May 07
2
[LLVMdev] DWARF unmangled subprog name (DW_AT_name)
On Wed, May 7, 2014 at 11:33 AM, Eric Christopher <echristo at gmail.com>wrote:
> Have you checked out llvm-symbolize? It's what the asan folk
> (including Alexey) have created for backtrace symbolication.
>
Yeah, we potentially can add some kind of option: "llvm-symbolizer
-print-short-function-names", I don't yet see why this would be valuable.
What's wrong
2018 Mar 26
0
Interest in integrating a linux perf JITEventListener?
...uint64_t Addr = *AddrOrErr;
> + uint64_t Size = P.second;
> +
> + // According to spec debugging info has to come before loading the
> + // corresonding code load.
> + DILineInfoTable Lines = Context.getLineInfoForAddressRange(
> + Addr, Size, FileLineInfoKind::AbsoluteFilePath);
> + NotifyDebug(Addr, Lines);
> +
> + NotifyCode(Name, Addr, Size);
> + }
> +
> + Dumpstream->flush();
> +}
> +
> +void PerfJITEventListener::NotifyFreeingObject(const ObjectFile &Obj) {
> + /* perf currently doesn't have an interface for unloadin...
2016 Dec 29
1
Interest in integrating a linux perf JITEventListener?
Having something like this available in tree would definitely be
useful. For simplicity, why don't we start with support for the second
style? This is the long term useful one and would be a good starting
point for getting the code in tree. Can you give a pointer to the patch
so that I can assess the rough complexity? If it's simple enough, I'd
be happy to help get it reviewed
2017 Feb 02
0
Interest in integrating a linux perf JITEventListener?
Hi,
On 2016-12-29 13:17:50 -0800, Philip Reames wrote:
> Having something like this available in tree would definitely be
> useful.
Cool.
> For simplicity, why don't we start with support for the second style? This
> is the long term useful one and would be a good starting point for getting
> the code in tree.
Works for me.
> Can you give a pointer to the patch so that