Thank you for this information.
If so, is there any way to grasp which kinda data throw in and out in LLVM as shown in such a way in gdb?
Thanks,
Seung Jae Lee
Seung Jae Lee wrote:
Thank you for this information.
If so, is there any way to grasp which kinda data throw in and out in LLVM as shown in such a way in gdb?
I don't understand the question. Are you trying to debug an LLVM pass,
or are you trying to debug a program generated by LLVM?
You can use gdb on the LLVM tools (such as opt) to debug LLVM passes,
and you can run gdb on code statically compiled with the LLVM compilers,
too (although I don't know how complete the debug information will be in
the resulting executable).
-- John T.
Hey, Seung,
I think what you want is to use gdb to debug your pass, isn' it? If you are running your pass with llc (or opt, etc), you only have to do "gdb llc", and the debugger will load all your files and libraries. Then you can set breakpoints, and do everything that gdb does. Also, many times I have been using gdb to debug the assembly code produced by llc. You only have to compile it with -g, and it will work, e.g. gcc p.s -o p.exe ; gdb p.exe.
Fernando