> the dynamic code generated using the
> DynamicMethod class [...] is subject to
> garbage collection

> dynamically generated code
> is stored on the managed heap.

> If it does, it means that its address may shift (during a GC when the heap
> is compacted), which means that the second DynamicMethod that uses it may
> contain a call (Opcodes.Call) to a method that no longer exists in the
> specified address (after JITting, of course).

"Amir Shitrit" <AmirShitrit@discussions.microsoft.com> wrote in message
news:F89D7881-4D21-435C-AFF8-AA5F4EE05777@microsoft.com...
> Hi.
> According to my understanding, the dynamic code generated using the
> DynamicMethod class is part of the DynamicMethod instance and is subject
> to
> garbage collection just like any other object, once no longer used.
> This must mean (correct me if I'm wrong) that the dynamically generated
> code
> is stored on the managed heap.
> My question is this: if I have a DynamicMethod that calls another
> DynamicMethod, how is it possible that the dynamically generated code
> resides
> on the managed heap?
> If it does, it means that its address may shift (during a GC when the heap
> is compacted), which means that the second DynamicMethod that uses it may
> contain a call (Opcodes.Call) to a method that no longer exists in the
> specified address (after JITting, of course).
>
> Thanks.