.net - MSIL and Dissassembly for debugging -
i have plenty of experience debugging .net applications using visual studio debugger. have experience using windbg identify , resolve memory leaks.
i don't have experience using ildam or .net dissassembly (displays assembly code generated jit) investigate problems. when ildasm/.net dissassebly used investigate problems? there educational purposes developers want invent own language)? suspect not.
i have investigated online e.g. here: http://msdn.microsoft.com/en-us/library/aa309387%28v=vs.71%29.aspx, have not found answer.
when want see disassembled code go ildasm tool , give mapped path of dll , see disassembled code in tool
check this out.
from microsoft site:-
this tutorial offers introduction msil disassembler (ildasm.exe) included .net framework sdk. ildasm.exe parses .net framework .exe or .dll assembly, , shows information in human-readable format. ildasm.exe shows more microsoft intermediate language (msil) code — displays namespaces , types, including interfaces. can use ildasm.exe examine native .net framework assemblies, such mscorlib.dll, .net framework assemblies provided others or created yourself. .net framework developers find ildasm.exe indispensable.
Comments
Post a Comment