依赖性Walker:打开文件时出错 [英] Dependency Walker: Error Opening File

查看:337
本文介绍了依赖性Walker:打开文件时出错的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在使用Dependency Walker来尝试解决.dll错误。我有一个主要的项目,包括许多图书馆。 Dependency Walker在4 .dll上显示错误:

I am using Dependency Walker to try and resolve a .dll error. I have a main project that includes many libraries. Dependency Walker shows an error on 4 .dlls:

打开文件时出错。系统找不到指定的文件(2)。

这是有趣的,因为Visual Studio的链接器的输出清楚地显示了库已经找到。 .exe中的所有内容都已正确链接(所有符号都已解决)。当我启动应用程序时,我收到Windows错误:

Which is funny because the output of Visual Studio's linker clearly shows that the libraries have been found. Everything in the .exe is linked properly (all symbols are resolved). When I start the application I get a Windows error:

程序已停止工作。

我正在使用与此问题中讨论的相同的API: Win32 DLL导入问题(DllMain)。如果我在调试模式下构建,我得到了关于内存初始化的引用的错误。

I'm using the same API that was discussed in this question: Win32 DLL importing issues (DllMain). If I build in debug mode I get the error that is quoted about memory initialization.

是否包含.dlls或Dependency Walker无法看到.dlls的问题?这是因为相关库是导入库吗?

Are the .dlls being included or is the problem that Dependency Walker can't see the .dlls? Is this because the relevant libraries are import libraries?

推荐答案

.dlls被包含在内。依赖性沃克只是不知道在哪里找到文件。将库目录添加到系统 PATH 变量允许Dependency Walker查找库。

The .dlls were being included. Dependency Walker just didn't know where to find the files. Adding the library directories to the system PATH variable allowed Dependency Walker to find the libraries.

这篇关于依赖性Walker:打开文件时出错的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆