How to query profiler instrumented IL code address using Windbg and SOS extension?

Asked Sep 14 '22 at 15:33

Active Sep 15 '22 at 09:23

Viewed 88 times

I have been debugging a .Net framework (4.8) CLR profiler codebase using Windbg and extension SOS.

I am starting the target application debug binary through windbg and after the instrumentation has happened for a function (within assembly mscorlib) I use the DumpIL command with the target function's MethodDesc address which gives me the IL opcode listing and the IL address but this is same as the address(RVA) and the IL opcodes which was present in the original assembly as seen through ILDASM.

I found out that this is a known issue and was fixed in the .Netcore SOS extension. Refer Github Issue link

I have tried out another tool dnSpy but see the same issue here as well.

Are there any .Net framework specific debugging tools which can provide the address of the profiler modified IL code or the function IL opcode listing?

edited Sep 15 '22 at 09:23

asked Sep 14 '22 at 15:33

prasen_b

Measuring performance in the debug build? – Thomas Weller Sep 15 '22 at 14:37
1

@ThomasWeller - Not interested in performance of the target app. Debugging to understand the profiler code base. – prasen_b Sep 16 '22 at 11:32

How to query profiler instrumented IL code address using Windbg and SOS extension?

0 Answers0