Ошибка при вызове loadlibrary не найдена указанная процедура

The Microsoft gflags tool will always tell you exactly what dependency is failing to load and why.

Run gflags -i your_application.exe +sls. After that execute the application under the debugger to capture the loader traces.

gflags is part of Debugging Tools — you might check in C:Program Files (x86)Windows Kits10Debuggersx64 to see if you already have it. You can add that directory to your path, or just execute gflags from that directory in cmd.exe.

For example, after running gflags, put a break point on the ::LoadLibrary(_T("foo")) call and step over it while looking for loader errors in your Visual Studio output window, e.g.

4b00:396c @ 479194074 - LdrpSnapThunk - ERROR: Procedure "?SetObject@vis_DollarMap@@QEAAXHPEAX@Z" could not be located in DLL "bar.dll"
First-chance exception at 0x0000000077307EF8 (ntdll.dll) in your_application.exe: 0xC0000139: Entry Point Not Found.
4b00:396c @ 479194074 - LdrpGenericExceptionFilter - ERROR: Function LdrpSnapIAT raised exception 0xc0000139
    Exception record: .exr 0000000000129070
    Context record: .cxr 0000000000128B80
4b00:396c @ 479194074 - LdrpHandleOneOldFormatImportDescriptor - ERROR: Snapping the imports from DLL "C:test64Debugfoo.DLL" to DLL "C:test64Debugbar.dll" failed with status 0xc0000139

This means that during the load of foo.dll, the dependency bar.dll was imported, and the bar.dll import failed.

The dependency import failed because the procedure ?SetObject@vis_DollarMap@@QEAAXHPEAX@Z was missing — you can demangle that to public: void __cdecl vis_DollarMap::SetObject(int,void * __ptr64) __ptr64.

You probably have the wrong version of a dependency — maybe you need to rebuild the dependency to get it up to date.

Run gflags -i your_application.exe -sls afterwards to disable the loader traces.

The Microsoft gflags tool will always tell you exactly what dependency is failing to load and why.

Run gflags -i your_application.exe +sls. After that execute the application under the debugger to capture the loader traces.

gflags is part of Debugging Tools — you might check in C:Program Files (x86)Windows Kits10Debuggersx64 to see if you already have it. You can add that directory to your path, or just execute gflags from that directory in cmd.exe.

For example, after running gflags, put a break point on the ::LoadLibrary(_T("foo")) call and step over it while looking for loader errors in your Visual Studio output window, e.g.

4b00:396c @ 479194074 - LdrpSnapThunk - ERROR: Procedure "?SetObject@vis_DollarMap@@QEAAXHPEAX@Z" could not be located in DLL "bar.dll"
First-chance exception at 0x0000000077307EF8 (ntdll.dll) in your_application.exe: 0xC0000139: Entry Point Not Found.
4b00:396c @ 479194074 - LdrpGenericExceptionFilter - ERROR: Function LdrpSnapIAT raised exception 0xc0000139
    Exception record: .exr 0000000000129070
    Context record: .cxr 0000000000128B80
4b00:396c @ 479194074 - LdrpHandleOneOldFormatImportDescriptor - ERROR: Snapping the imports from DLL "C:test64Debugfoo.DLL" to DLL "C:test64Debugbar.dll" failed with status 0xc0000139

This means that during the load of foo.dll, the dependency bar.dll was imported, and the bar.dll import failed.

The dependency import failed because the procedure ?SetObject@vis_DollarMap@@QEAAXHPEAX@Z was missing — you can demangle that to public: void __cdecl vis_DollarMap::SetObject(int,void * __ptr64) __ptr64.

You probably have the wrong version of a dependency — maybe you need to rebuild the dependency to get it up to date.

Run gflags -i your_application.exe -sls afterwards to disable the loader traces.

Страницы: [1]   Вниз

Страницы: [1]   Вверх

Microsoft gflags Инструмент всегда сообщит вам, какая зависимость не загружается и почему.

Run gflags -i your_application.exe +sls. После этого запустите приложение в отладчике, чтобы захватить следы погрузчика.

gflags является частью Инструменты отладки — вы можете зарегистрироваться C:Program Files (x86)Windows Kits10Debuggersx64 чтобы узнать, есть ли оно у вас. Вы можете добавить этот каталог в свой путь или просто выполнить gflags из этого каталога в cmd.exe.

Например, после запуска gflags установите точку останова на ::LoadLibrary(_T("foo")) вызовите и перешагните через него, ища ошибки загрузчика в окне вывода Visual Studio, например

4b00:396c @ 479194074 - LdrpSnapThunk - ERROR: Procedure "?SetObject@vis_DollarMap@@QEAAXHPEAX@Z" could not be located in DLL "bar.dll"
First-chance exception at 0x0000000077307EF8 (ntdll.dll) in your_application.exe: 0xC0000139: Entry Point Not Found.
4b00:396c @ 479194074 - LdrpGenericExceptionFilter - ERROR: Function LdrpSnapIAT raised exception 0xc0000139
    Exception record: .exr 0000000000129070
    Context record: .cxr 0000000000128B80
4b00:396c @ 479194074 - LdrpHandleOneOldFormatImportDescriptor - ERROR: Snapping the imports from DLL "C:test64Debugfoo.DLL" to DLL "C:test64Debugbar.dll" failed with status 0xc0000139

Это означает, что при загрузке foo.dll, зависимость bar.dll был импортирован, а bar.dll сбой импорта.

Импорт зависимости завершился неудачно, поскольку процедура ?SetObject@vis_DollarMap@@QEAAXHPEAX@Z пропал — вы можете разобрать что к public: void __cdecl vis_DollarMap::SetObject(int,void * __ptr64) __ptr64.

Вероятно, у вас неправильная версия зависимости — возможно, вам нужно перестроить зависимость, чтобы обновить ее.

Run gflags -i your_application.exe -sls потом отключить следы загрузчика.