In theory you don't have to do anything special to debug some JIT-ed code as everything should just work (based on the gdb jit interface). In practice I tried it out a few days ago and it wasn't working at all even in the case when the application is launched under LLDB (not with attach). LLDB was understanding the eh_frame for the JIT-ed code but didn't found the debug info for unknown reason. We should investigate it and try to fix it sometime. We (lldb for android developers) plan to do it sometime but if you are interested in it then please feel free to take a look and let us know if you have any question.
Tamas On Thu, Nov 19, 2015 at 8:40 AM haifeng_q via lldb-dev < lldb-dev@lists.llvm.org> wrote: > hi, > process A generate function Func1 code with llvm jit compiler, and calls > Func1. modeled on "Kaleidoscope: Adding Debug Information" add debug > information. how to use LLDB to attach process A to debug this function, add > a breakpoint in the function? > > thanks! > _______________________________________________ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev >
_______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
