If you are building/debugging a DLL, the most typical reason is that the DLL
is loaded from a wrong location (e.g. an old version gets loaded).
When debugging, open Modules window (Debug | Modules) and check
the path to the DLL.
If you are working with an .exe, it is possible that wrong executable is specified
in project settings. Compare the following settings:
- Project | Settings | Debug | General | Executable for debug session
- Project | Settings | Link | General | Output file name
They must point to the same .exe file. And again, Modules window can
be used to check the path to the .exe file when debugging.
Also I would recommend to use /pdbtype:con linker option
to merge all vc60.pdb files into the final pdb file of the executable module:
- Project | Settings | Link | Debug | "Separate types" - must be unchecked
'tool > VS6' 카테고리의 다른 글
VC Debugger가 쓰레드 디버깅 시에 hang되는 문제에 대한 해결 방안 (0) | 2010.06.29 |
---|---|
간단한 팁들... (0) | 2009.07.10 |
VB6 패키지배포 마법사로 작성된 CAB파일 문제 (0) | 2009.07.07 |
.dsw파일을 열 때 새 프로그램으로 열기 (0) | 2009.06.22 |
원인모를 문제해결 경험들 (0) | 2009.06.17 |