You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 1, 2020. It is now read-only.
I'm looking at how to debug a native program using gdb/lldb. On AMD64, you can actually step into the source code of managed code. However it does not seem possible to list all locals and arguments. From what I can gather, the debugging info seems to be generated by RyuJit, does it means that for the non-C++ backends, it will rely on RyuJit for debug info and that therefore any improvements on this topic should be done in CoreCLR?
The text was updated successfully, but these errors were encountered:
RyuJIT has everything required for this. It generates IL->native map for both code and local variables.
The missing parts are in CoreRT and ObjectWriter (that lives in llilc repo). Merge the source code -> IL map and IL->native map and write the result as PDB or DWARF.
I'm looking at how to debug a native program using gdb/lldb. On AMD64, you can actually step into the source code of managed code. However it does not seem possible to list all locals and arguments. From what I can gather, the debugging info seems to be generated by RyuJit, does it means that for the non-C++ backends, it will rely on RyuJit for debug info and that therefore any improvements on this topic should be done in CoreCLR?
The text was updated successfully, but these errors were encountered: