Hello All
I am trying to analyze Julia code, and I was interested to know if there is a seamless method to debug Julia development code. Using the gdb, I am able to add breakpoints and visualize the Julia “C” files, but the debugging process naturally terminates as soon as the control steps into a “.jl” file. Is there some nice hack that facilitates debugging Julia code.
PS: I am new to Julia development, so pardon me if the question seems naive.
I’m not aware of anything available to step in to Julia code from LLDB or GDB right now.
Julia uses the GDB JIT registrar protocol if available, so you should at least get quasi-mangled (usually some numbers attached) Julia function names in backtraces. On Mac, this works well with 0.6 and recent LLDB versions.
By the way, be sure to read the devdocs if you haven’t, for some related suggestions:
https://docs.julialang.org/en/stable/#Developer-Documentation-1
I have used [Gallium] (https://github.com/Keno/Gallium.jl) in the past. It works beautifully. Unfortunately, it does not support 0.6 yet. Documentation is limited, but you get an intro via this video.
Thanks! Gallium helped a bit. Is there a way to determine which function is called when Gallium returns “intrinsic function #”.