search for: mcjit'ed

Hi, I’m wondering if it’s possible to debug code JIT’ed with the newer ORC JIT. The LLVM documentation has a page at llvm.org/docs/DebuggingJITedCode.html <http://llvm.org/docs/DebuggingJITedCode.html> showing an example of using gdb to debug MCJIT’ed code, but has no mention of ORC JIT. From searching around online I’ve gotten the impression that ORC JIT does *not* support providing debugging information to attached debuggers, but no definitive source. Is it the case that ORC JIT in fact does support debugging, and if so, are there examples...

Hi Connor, ...The LLVM documentation has a page at > llvm.org/docs/DebuggingJITedCode.html > showing an example of using gdb to debug MCJIT’ed code, but has no mention > of ORC JIT. What debugging support MCJIT has is provided by the RuntimeDyld utility, which ORC shares. I would expect anything in that document to apply to ORC as well, though I haven't tested it personally. For what it's worth, this is something I'm...

Hi, I ran into a problem migrating cling (finally!) to MCJIT: When an ("outer") MCJIT's finalization / llvm::RuntimeDyldImpl::resolveExternalSymbols() is called and a symbol is not known, cling can help by loading the suitable library and providing the symbol. It compiles the relevant C++ header as part of loading the library. This compilation...

...mory and point the debugger at that. > > Hi Eric, thanks for answering. > Suppose I would like to prototype adding such functionality to LLVM - where in the code would be the best place to start? Any existing interfaces that should be reused/implemented/extended here? lib/ExecutionEngine/MCJIT and lib/ExecutionEngine/RuntimeDyld. The old JIT (lib/ExecutionEngine/JIT) probably has some bits in it for telling the debugger where the debug info lives that could be repurposed, or at minimum would be good reading for general "what's involved" sort of information gathering. If th...

> > So where should I look for adding such support? Is MC JIT the direction? > Does it purport to emit DWARF as well as executable code? Any pointers to > relevant places in the code would be most appreciated. > > > MC JIT is the direction that the JIT will be going in the future. Right now > any debugging emission is minimal at best. My ideas here would be to emit > the

...ted 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 MCJIT has is provided by the RuntimeDyld utility, > > which ORC shares. I would expect anything in that document to apply to > ORC > > as well, though I haven't tested it personally. > > I'm pretty sure that's not the case, at least not with any simple > orcjit tutoria...