2008년 02월 28일
VS2005, Dependency Walker, 의존성 탐색기
Why Use Dependency Walker?
Have you ever...
* ... wondered why an application or module was failing to load?
* ... wondered what minimum set of files are required to run a particular application or load a particular DLL?
* ... wondered why a certain module was being loaded with a particular application?
* ... wanted to know what functions are exposed by a particular module,
and which ones are actually being called by other modules?
* ... wanted to know the parameter and return types of exported C++ functions?
* ... wanted to remove all dependencies for a given module?
* ... wanted to know the complete path of all the modules being loaded for a particular application?
* ... wanted to know all the base addresses of each module being loaded for a particular application?
What about versions? Or maybe CPU types?
* ... received one of the following errors...
- The dynamic link library BAR.DLL could not be found in the specified path...
- The procedure entry point FOO could not be located in the dynamic link library BAR.DLL.
- The application or DLL BAR.DLL is not a valid Windows image.
- The application failed to initialize properly.
- Initialization of the dynamic link library BAR.DLL failed. The process is terminating abnormally.
- The image file BAR.EXE is valid, but is for a machine type other than the current machine.
- Program too big to fit in memory.
프로그램의 위치
이 폴더에는 그 외에 WindDiff.exe, Where.exe등 다양한 툴들이 들어 있다.
프로그램 실행 화면 스크린 샷
Have you ever...
* ... wondered why an application or module was failing to load?
* ... wondered what minimum set of files are required to run a particular application or load a particular DLL?
* ... wondered why a certain module was being loaded with a particular application?
* ... wanted to know what functions are exposed by a particular module,
and which ones are actually being called by other modules?
* ... wanted to know the parameter and return types of exported C++ functions?
* ... wanted to remove all dependencies for a given module?
* ... wanted to know the complete path of all the modules being loaded for a particular application?
* ... wanted to know all the base addresses of each module being loaded for a particular application?
What about versions? Or maybe CPU types?
* ... received one of the following errors...
- The dynamic link library BAR.DLL could not be found in the specified path...
- The procedure entry point FOO could not be located in the dynamic link library BAR.DLL.
- The application or DLL BAR.DLL is not a valid Windows image.
- The application failed to initialize properly.
- Initialization of the dynamic link library BAR.DLL failed. The process is terminating abnormally.
- The image file BAR.EXE is valid, but is for a machine type other than the current machine.
- Program too big to fit in memory.
프로그램의 위치
이 폴더에는 그 외에 WindDiff.exe, Where.exe등 다양한 툴들이 들어 있다.
프로그램 실행 화면 스크린 샷
☞ 내 이글루에 이 글과 관련된 글 쓰기 (트랙백 보내기) [도움말]