Home/ Questions/Q 775233
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T19:15:26+00:00

In trying to find the possible cause of an exception, I’m following a code

  • 0

In trying to find the possible cause of an exception, I’m following a code path using Reflector. I’ve got deeper and deeper, but ended up at a method call that looks like:

[MethodImpl(MethodImplOptions.InternalCall)]
private extern void SomeMethod(int someParameter);

This markup on the method tells the framework to call a C++ function somewhere. Is there any way to find out what method actually gets called, and in turn what else is likely to be called?

NB: I don’t really want to see the source code of this method, I just want to know the possible things that could throw the exception I am seeing that originates out of this method call.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Internal calls end up making a call to a C++ function in the CLR. You can find them back in the Rotor source code. Look at clr\src\vm\ecall.cpp to find the mapping from the .NET visible name to the CLR function name. Beware that the source is getting dated.

    • 0