Yes, you can use WinDbg + SOS to parse the code generated by JIT. More specifically, you may find that the !u command is especially useful for your needs:
Displays an annotated disassembly of the managed method, indicated either by the pointer to the MethodDesc structure for the method, or by the code address inside the method body. The U command displays the entire method from start to finish, with annotations that convert metadata tokens into names.
source share