-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debugging support for JIT code #1501
Comments
As I mentioned to Leonard on IRC, one way to do the trace feature is to:
It might also be possible to specify a breakpoint from the debugger by calling a |
It would be far better to make the JIT emit DWARF information to memory, then inform GDB about it. I |
tcc uses stabs. I don't know how to inform gdb to load something from memory. |
I believe this is done by now. There's now support for both gdb and oprofile. |
mentioned in issue llvm/llvm-bugzilla-archive#21523 |
mentioned in issue llvm/llvm-bugzilla-archive#45208 |
Extended Description
When debugging JIT code, I'd like to have some means to either step through code
using GDB or see a trace of JITed code.
The text was updated successfully, but these errors were encountered: