R6034错误

[luoyunfeng1980]

目前程序中偶尔会弹出R6034错误，网上搜索都说是导出manifest文件的问题，如果是这个原因，这个错误应该是必现的，但是目前这个问题偶现，有点奇怪。在弹出错误的时候，抓了一个dmp文件，发现加载了一个当前目录下的msvcr90.dll，这肯定是不合理的，因为进程已经加载了WinSXS下的CRT库，而且就算要加载当前目录下的CRT，对于VC2008来说，CRT库一定要有配套的manifest文件才可以。难道弹出R6034就是因为加载了这个错误的msvcr90.dll？可是为什么会加载这个不正确的msvcr90.dll？

[luoyunfeng1980]

引用 1 楼 zhao4zhong1 的回复:

C Run-Time Libraries https://msdn.microsoft.com/en-us/library/abx4dbyh.aspx 学会使用depends.exe查看exe依赖的dll

查看过了，我的进程是MT选项编译的，使用了一个MD编译的CxImage库，depends.exe查看是依赖于WinSXS下的CRT，这肯定是正确的，这个进程不可能加载同级目录下的CRT，很奇怪，不知道为什么加载了。观察了以下，正常情况下只加载WinSXS下的CRT，也不会出错，不明白什么场景下竟然加载同级目录下的msvcr90.dll，然后就出错了，直接挂在crtmain，这肯定是和环境有关系的

[赵4老师]

C Run-Time Libraries https://msdn.microsoft.com/en-us/library/abx4dbyh.aspx 学会使用depends.exe查看exe依赖的dll

[赵4老师]

Dynamic-Link Library Search Order A system can contain multiple versions of the same dynamic-link library (DLL). Applications can control the location from which a DLL is loaded by specifying a full path, using DLL redirection, or by using a manifest. If none of these methods are used, the system searches for the DLL at load time as described in this topic. Standard Search Order The dynamic-link library (DLL) search order used by the system depends on whether safe DLL search mode is enabled or disabled. Windows Vista, Windows Server 2003, and Windows XP SP2: Safe DLL search mode is enabled by default. To disable this feature, create the HKLM\System\CurrentControlSet\Control\Session Manager\SafeDllSearchMode registry value and set it to 0. Calling the SetDllDirectory function effectively disables SafeDllSearchMode while the specified directory is in the search path and changes the search order as described in this topic. Windows XP and Windows 2000 SP4: Safe DLL search mode is disabled by default. To enable this feature, create the SafeDllSearchMode registry value and set it to 1. If SafeDllSearchMode is enabled, the search order is as follows: The directory from which the application loaded. The system directory. Use the GetSystemDirectory function to get the path of this directory. The 16-bit system directory. There is no function that obtains the path of this directory, but it is searched. The Windows directory. Use the GetWindowsDirectory function to get the path of this directory. The current directory. The directories that are listed in the PATH environment variable. Note that this does not include the per-application path specified by the App Paths registry key. If SafeDllSearchMode is disabled, the search order is as follows: The directory from which the application loaded. The current directory. The system directory. Use the GetSystemDirectory function to get the path of this directory. The 16-bit system directory. There is no function that obtains the path of this directory, but it is searched. The Windows directory. Use the GetWindowsDirectory function to get the path of this directory. The directories that are listed in the PATH environment variable. Note that this does not include the per-application path specified by the App Paths registry key. Note that versions of Windows prior to the ones listed at the beginning of this section do not support SafeDllSearchMode. For more information, see Legacy Search Order below. Alternate Search Order The standard search order used by the system can be changed by calling the LoadLibraryEx function with LOAD_WITH_ALTERED_SEARCH_PATH. The standard search order can also be changed by calling the SetDllDirectory function. Windows XP/2000 and Windows 2000 Server: Changing the standard search order by calling SetDllDirectory is not supported until Windows XP SP1 and Windows Server 2003. If you specify an alternate search strategy, its behavior continues until all associated executable modules have been located. After the system starts processing DLL initialization routines, the system reverts to the standard search strategy. The LoadLibraryEx function supports an alternate search order if the call specifies LOAD_WITH_ALTERED_SEARCH_PATH and the lpFileName parameter specifies an absolute path. Note that the standard search strategy and the alternate search strategy specified by LoadLibraryEx with LOAD_WITH_ALTERED_SEARCH_PATH differ in just one way: The standard search begins in the calling application's directory, and the alternate search begins in the directory of the executable module that LoadLibraryEx is loading. If SafeDllSearchMode is enabled, the alternate search order is as follows: The directory specified by lpFileName. The system directory. Use the GetSystemDirectory function to get the path of this directory. The 16-bit system directory. There is no function that obtains the path of this directory, but it is searched. The Windows directory. Use the GetWindowsDirectory function to get the path of this directory. The current directory. The directories that are listed in the PATH environment variable. Note that this does not include the per-application path specified by the App Paths registry key. If SafeDllSearchMode is disabled, the alternate search order is as follows: The directory specified by lpFileName. The current directory. The system directory. Use the GetSystemDirectory function to get the path of this directory. The 16-bit system directory. There is no function that obtains the path of this directory, but it is searched. The Windows directory. Use the GetWindowsDirectory function to get the path of this directory. The directories that are listed in the PATH environment variable. Note that this does not include the per-application path specified by the App Paths registry key. The SetDllDirectory function supports an alternate search order if the lpPathName parameter specifies a path. The alternate search order is as follows: The directory from which the application loaded. The directory specified by lpPathName. The system directory. Use the GetSystemDirectory function to get the path of this directory. The name of this directory is System32. The 16-bit system directory. There is no function that obtains the path of this directory, but it is searched. The name of this directory is System. The Windows directory. Use the GetWindowsDirectory function to get the path of this directory. The directories that are listed in the PATH environment variable. If the lpPathName parameter is an empty string, the call removes the current directory from the search order. SetDllDirectory effectively disables safe DLL search mode while the specified directory is in the search path. To restore safe DLL search mode based on the SafeDllSearchMode registry value and restore the current directory to the search order, call SetDllDirectory with lpPathName as NULL. Legacy Search Order Versions of Windows earlier than the ones listed under Standard Search Order do not support the SafeDllSearchMode value. The DLL search order is as follows: The directory from which the application loaded. The current directory. The system directory. Use the GetSystemDirectory function to get the path of this directory. The 16-bit system directory. There is no function that obtains the path of this directory, but it is searched. The Windows directory. Use the GetWindowsDirectory function to get the path of this directory. The directories that are listed in the PATH environment variable. Note that this does not include the per-application path specified by the App Paths registry key. See Also Dynamic-Link Library Redirection LoadLibrary LoadLibraryEx SetDllDirectory Side-by-side Components Send comments about this topic to Microsoft Build date: 8/15/2007