GetProcAddress does not find function in DLL

Question

I have a DLL and I want to call a function in it. I check the DLL using Dependency Walker and the result I got is:

 void U2U_Test(void)

This is the code that I wrote, but GetProcAddress() returns NULL:

typedef void(*U2U_Test_pointer)();

void  check() {

    HINSTANCE hGetProcIDDLL1 = LoadLibrary(_T("my_dll.dll"));

    if (hGetProcIDDLL1 == NULL)
        return;

    U2U_Test_pointer addr = (U2U_Test_pointer)GetProcAddress(hGetProcIDDLL1, "U2U_Test");

    if (addr == NULL)
        return;

    return addr();
}

You see the demangled name. The exported name should me mangled. — 273K, Aug 29 '21 at 05:40
`GetProcAddress` doesn't lie. That function named `U2U_Test` doesn't exist in the DLL you loaded. If you say it does, contact Microsoft as quickly as possible, as that is a bug that would affect millions of programs. — PaulMcKenzie, Aug 29 '21 at 05:41
Not related, but `return addr();` makes no sense in that function either. The function is `void`. That should be simply `addr();` — WhozCraig, Aug 29 '21 at 05:45
@S.M. you are right I should use use ?U2U_Test@@YAXXZ for function name, it solve the problem. — Sasan, Aug 29 '21 at 05:56
@PaulMcKenzie you are right, GetProcAddress doesn't lie, but I was looking for my mistake and by help of dear S.M. I found my mistake. — Sasan, Aug 29 '21 at 05:58
Dear @WhozCraig you are absolutely right, however I have many functions in that dll and I want to use a same pattern for all of the functions. Thanks for mentioning that. — Sasan, Aug 29 '21 at 06:00

score 0 · Answer 1 · answered Aug 29 '21 at 06:15

Depending on conventions and compiler used, the actual name exported in the DLL might not be exactly the same as the one you wrote in your source code. This phenomenon is commonly called name decoration or name mangling.

In fact you are guaranteed to have exactly the same name only if

Your compiler conforms to C conventions (probably it does)
The function is exported in C and not C++. Use extern "C" to specify it.
The calling convention is _cdecl (specify __cdecl in function declaration)

For example, when call convention is __stdcall instead of __cdecl, which is common for many windows DLLs (they often write WINAPI or CALLBACK instead of __sstdcall), the name of the exported function is often suffixed by @n where n is the number of bytes expected on the stack for parameters. In your case, it could be U2U_Test@0. Indications like __declspec(dllimport) and __declspec(dllexport) tell the compiler to automatically take care of that kind of thing when DLLs are imported/linked at compile time.

IN C++, complex name decoration is used in order to support methods, function overloading, templates and other features, and each compiler invented crazy naming schemes to make sure there won't ever be any clash. Because at DLL level, there's no template, no classes, only a list of exported symbols indexed by their name or an ID. That's the reason why most DLLs are exported in C and why most header files declare functions coming from DLL inside a extern "C" { ... } block.

GetProcAddress does not find function in DLL

1 Answers1