Getting IL and Native Code Addresses...

[davidcorbin-atmosera]

// Unfortunately there's not a great way to get the size of the code, or the end address. // This is partly due to the fact that we don't *have* to put all the JIT'ed code into one // contiguous chunk, though I think an implementation detail is that we actually do. // You are supposed to do code flow analysis like "uf" in windbg to find the size, but // in practice you can use the IL to native mapping:
However, the related code does NOT look right.... It seems to be getting the memory for a METHOD, and that method may not even be related to the TYPE (it is always looking at GetHashCode)...

Am I Missing something?

[leculver]

Can you point me to the code you are referring to?

[davidcorbin-atmosera]

@leculver - Thanks for the response. I think it was one of the samples, and am currently going back to find the original source material. This is hampered because many of the links (e.g. those on the FAQ.md page) are broken (they appear to still reference a "master" branch which has not been rtenamed to "main)....That should probably be a distinct issue...

I will keep you posted...

UPDATE: I have found a site that references the martial I am talking about, but is not the original source (still looking) https://experimentation.readthedocs.io/en/latest/MachineCode/. Seems like there are a "bunch of funnies"

UPDATE2: Apparently (from what I can determine) it was here: https://github.com/microsoft/dotnet-samples which has a now broken link to https://github.com/microsoft/dotnet-samples/blob/master/Microsoft.Diagnostics.Runtime/CLRMD - I have found this information from various forks... still trying to determine where I originally got it from, but hopefully this provides context.

[leculver]

Thanks! I'm just now starting a sprint of ClrMD work. I'll take a look at this as soon as I'm done with the current in-flight NativeAOT support...but that may take me a few days to churn through. I'll see if I can get the links updated too. There's already an issue tracking that.