Displaying 20 results from an estimated 36 matches for "notifyobjectemit".
2013 Nov 13
2
[LLVMdev] Stack traces from JIT code
Hi Andy,
In the NotifyObjectEmitted method of our derived JITEventListener class we
use the begin_symbol() iterator to walk the object's symbols looking for
functions and only functions marked with ExternalLinkage seem to show up.
I'm not sure how I would access the Dwarf info from within there, is there
a way?
Thanks,
An...
2013 Nov 13
3
[LLVMdev] Stack traces from JIT code
We implemented a similar solution for handling crashes in production but
one issue we came across with MCJIT was that the NotifyFunctionEmitted call
from the old JIT was replaced with NotifyObjectEmitted. The ObjectImage
used by NotifyObjectEmitted does have a way of iterating symbols but
non-external functions used in the module didn't seem to appear in this
list so we were left with some gaps in our symbol handling coverage when
execution involved these. If there's a way around it that...
2013 Nov 13
0
[LLVMdev] Stack traces from JIT code
...elJITEvents). It uses the debug info to find function names.
-Andy
From: Andrew MacPherson [mailto:andrew.macp at gmail.com]
Sent: Wednesday, November 13, 2013 1:12 PM
To: Kaylor, Andrew
Cc: Reid Kleckner; llvmdev at cs.uiuc.edu
Subject: Re: [LLVMdev] Stack traces from JIT code
Hi Andy,
In the NotifyObjectEmitted method of our derived JITEventListener class we use the begin_symbol() iterator to walk the object's symbols looking for functions and only functions marked with ExternalLinkage seem to show up. I'm not sure how I would access the Dwarf info from within there, is there a way?
Thanks,
An...
2013 Nov 13
0
[LLVMdev] Stack traces from JIT code
>From NotifyObjectEmitted you should be able to get to any function that's visible via either the ELF headers or the DWARF information. Do you have functions that don't show up in either of those places?
-Andy
From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Andrew MacP...
2018 Mar 08
2
[PDB] [JIT] Write to PDB file when COFFObjectFile is emitted by JIT
Is it possible to write a .pdb file containing the debug info stored in a
COFFObjectFile once the NotifyObjectEmitted is triggered by the JIT
compiler ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180308/3c25cddd/attachment.html>
2017 Aug 24
1
Invalid Signature of orc::RTDyldObjectLinkingLayer::NotifyLoadedFtor
...^
It refers to llvm::LoadedObjectInfo base class in llvm/DebugInfo/DIContext.h
instead of llvm::RuntimeDyld::LoadedObjectInfo in
llvm/ExecutionEngine/RuntimeDyld.h
I think it should actually use the derived
RuntimeDyld::LoadedObjectInfo, as this is what listeners expect:
$ grep -h -r -A 1 "NotifyObjectEmitted("
./include/llvm/ExecutionEngine/JITEventListener.h
virtual void NotifyObjectEmitted(const object::ObjectFile &Obj,
const RuntimeDyld::LoadedObjectInfo
&L) {}
It doesn't break OrcMCJITReplacement as it duplicates the issue and the
Info param...
2015 Jun 04
2
[LLVMdev] MCJit interface question
When we were using MCJIT, I could do this:
// Attach the event listener
Context.EE->RegisterJITEventListener(
LLILCJitEventListener::createLLILCJitEventListener(
new LLILCJitEventWrapper(&Context)));
The event listeners listened for when an object is emitted (NotifyObjectEmitted), and that’s when we’d go through and extract debug info from the ObjectFile. Now, I imagine I’d need to add some sort of layer, I’m just not sure when, where or how to get that set up, and am looking for some guidance on it.
From: Joseph Tremoulet
Sent: Thursday, June 4, 2015 11:29 AM
To: Mich...
2018 Mar 14
2
[PDB] [JIT] Write to PDB file when COFFObjectFile is emitted by JIT
...ich debugger do you plan to
> use?
>
> -- Lang.
>
>
> On Thu, Mar 8, 2018 at 4:23 AM, Vivien Millet via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
>> Is it possible to write a .pdb file containing the debug info stored in a
>> COFFObjectFile once the NotifyObjectEmitted is triggered by the JIT
>> compiler ?
>>
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>>
>>
>
-------------- next part...
2018 Mar 10
0
[PDB] [JIT] Write to PDB file when COFFObjectFile is emitted by JIT
...e aim to be able to debug JIT'd code? Which debugger do you plan to
use?
-- Lang.
On Thu, Mar 8, 2018 at 4:23 AM, Vivien Millet via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Is it possible to write a .pdb file containing the debug info stored in a
> COFFObjectFile once the NotifyObjectEmitted is triggered by the JIT
> compiler ?
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
>
-------------- next part --------------
An HTML attachment wa...
2017 Oct 11
2
Debugging JIT'ed code with ORC JIT?
HI Yichao,
RTDyldObjectLinkingLayer has a NotifyObjectLoaded hook that you can use to
call NotifyObjectEmitted on your GDBRegistrationListener.
If code is going to be unloaded we would have to add an extra hook to call
NotifyFreeingObject -- that seems totally reasonable to add.
-- Lang.
On Wed, Oct 11, 2017 at 10:44 AM, Yichao Yu <yyc1992 at gmail.com> wrote:
> > What debugging support...
2018 Mar 14
0
[PDB] [JIT] Write to PDB file when COFFObjectFile is emitted by JIT
...?
>>
>> -- Lang.
>>
>>
>> On Thu, Mar 8, 2018 at 4:23 AM, Vivien Millet via llvm-dev <
>> llvm-dev at lists.llvm.org> wrote:
>>
>>> Is it possible to write a .pdb file containing the debug info stored in
>>> a COFFObjectFile once the NotifyObjectEmitted is triggered by the JIT
>>> compiler ?
>>>
>>> _______________________________________________
>>> LLVM Developers mailing list
>>> llvm-dev at lists.llvm.org
>>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>>>
>>&g...
2018 Apr 01
2
[Dwarf] Register a local variable in DIBuilder and locate it later with a DwarfContext
...C++ with
IRBuilder::CreateAlloca.
My goal is that one :
- Generate machine code with an instance of the class 'IRBuilder'
- Emit 'ObjFile' class instance with MCJIT
- Create a DwarfContext instance directly from the emitted ObjFile object
(DwarfContextInMemory) (on JitEventListener::NotifyObjectEmitted)
- Use this DwarfContext to step into my home made runtime debugger.
Now I can perform step over/into/out in my debugger using the DwarfContext
instance without problem, but I'm still stuck on how
to watch my local variables in my debugger (i can't figure out how to
locate them in regis...
2013 Nov 13
0
[LLVMdev] Stack traces from JIT code
Writing your own JITEventListener is probably the best way to capture
traces from production. Using the existing gdb/JIT interface support is
probably far too heavyweight for production. If you roll your own, you can
record the PC ranges efficiently and that should be good enough to capture
traces from production.
On Tue, Nov 12, 2013 at 2:56 PM, Priyendra Deshwal
<deshwal at
2014 Sep 18
5
[LLVMdev] VEX prefixes for JIT in llvm 3.5
...d and used a
>> MCDisassembler to disassemble the stream (with my own custom
>> annotators), and redirected the output to the relevant place for
>> auditing of our app.
>>
>> With MCJIT I notice that NotifyFunctionEmitted is gone
>> (understandably) and so I hook NotifyObjectEmitted. I then run through
>> all the function symbols and dump them as before. Yay. Except that in
>> MCJIT terms the linking hasn't happened, so all the globals and
>> external functions are all zeros at this point. (If I hackily observe
>> the same code later on I see th...
2018 Mar 14
1
[PDB] [JIT] Write to PDB file when COFFObjectFile is emitted by JIT
...>>>
>>>
>>> On Thu, Mar 8, 2018 at 4:23 AM, Vivien Millet via llvm-dev <
>>> llvm-dev at lists.llvm.org> wrote:
>>>
>>>> Is it possible to write a .pdb file containing the debug info stored in
>>>> a COFFObjectFile once the NotifyObjectEmitted is triggered by the JIT
>>>> compiler ?
>>>>
>>>> _______________________________________________
>>>> LLVM Developers mailing list
>>>> llvm-dev at lists.llvm.org
>>>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev...
2015 May 29
2
[LLVMdev] MCJit interface question
...uot;tight coupling" of RuntimeDyld with CoreCLR's particular interface. (and note that this is really two options, in that the code to separate out the per-function EH frame contribution could go in either the client memory manager or in the loader.)
2. Add a notification similar to NotifyObjectEmitted, but which runs just before the call to Dyld.loadObject. Something like NotifyObjectPreLoaded. The LLILC-specific MemoryManager could use this hook to scan the object::ObjectFile and pass whatever it needs to the CoreCLR. This seems like a decent option to me, but I don't know if it would...
2013 Nov 12
2
[LLVMdev] Stack traces from JIT code
[Resending this email after subscribing to the group. Got an error message
the previous time around]
Hey guys,
In our project we have the following workflow:
- Given a user request, we construct a C++ program to service the request
- We create a compiler invocation to compile that program into an IR module
- We use JIT (and optionally MCJIT) to convert the IR into executable code
and run it
2014 Sep 17
2
[LLVMdev] VEX prefixes for JIT in llvm 3.5
...IT I used JITEventListener's NotifyFunctionEmitted and used a
MCDisassembler to disassemble the stream (with my own custom
annotators), and redirected the output to the relevant place for
auditing of our app.
With MCJIT I notice that NotifyFunctionEmitted is gone
(understandably) and so I hook NotifyObjectEmitted. I then run through
all the function symbols and dump them as before. Yay. Except that in
MCJIT terms the linking hasn't happened, so all the globals and
external functions are all zeros at this point. (If I hackily observe
the same code later on I see the linker has appropriately populated...
2018 Apr 02
0
[Dwarf] Register a local variable in DIBuilder and locate it later with a DwarfContext
...eAlloca.
> My goal is that one :
> - Generate machine code with an instance of the class 'IRBuilder'
> - Emit 'ObjFile' class instance with MCJIT
> - Create a DwarfContext instance directly from the emitted ObjFile object
> (DwarfContextInMemory) (on JitEventListener::NotifyObjectEmitted)
> - Use this DwarfContext to step into my home made runtime debugger.
>
> Now I can perform step over/into/out in my debugger using the DwarfContext
> instance without problem, but I'm still stuck on how
> to watch my local variables in my debugger (i can't figure out how...
2015 Jun 04
2
[LLVMdev] MCJit interface question
...uot;tight coupling" of RuntimeDyld with CoreCLR's particular interface. (and note that this is really two options, in that the code to separate out the per-function EH frame contribution could go in either the client memory manager or in the loader.)
2. Add a notification similar to NotifyObjectEmitted, but which runs just before the call to Dyld.loadObject. Something like NotifyObjectPreLoaded. The LLILC-specific MemoryManager could use this hook to scan the object::ObjectFile and pass whatever it needs to the CoreCLR. This seems like a decent option to me, but I don't know if it would...