Home > OS >  R6034 error
R6034 error

Time:10-02


Currently in the program will pop up occasionally R6034 error, online search all export manifest file problem, if it is for this reason that this error should be will now, but at present the problem now, a bit odd, in the pop-up error, caught a DMP file, found that loading a current directory msvcr90. DLL, it definitely is not reasonable, because the process has loaded the WinSXS CRT libraries, and even to load the current directory of the CRT, for VC2008, CRT libraries must have a matching can manifest, don't pop-up R6034 is for loading the wrong msvcr90. DLL? But, why will load the incorrect msvcr90 DLL?

CodePudding user response:

C the Run - Time Libraries https://msdn.microsoft.com/en-us/library/abx4dbyh.aspx

Learn how to use the depends. Exe view exe dependent DLL

CodePudding user response:

reference 1st floor zhao4zhong1 response:
C Run - Time Libraries https://msdn.microsoft.com/en-us/library/abx4dbyh.aspx

Learn how to use the depends. Exe view exe dependent DLL

See, my process is MT the compiler options, and the compiler USES a MD CxImage library, depends. Exe view is dependent on the WinSXS CRT, this must be correct, this process can't be loaded at the same level directory of CRT, very strange, don't know why loaded, observe the following, under normal circumstances only under loading WinSXS CRT, also won't go wrong, don't know what scenario should load directory msvcr90. At the same level DLL, and then make a mistake, hanging crtmain directly, it must be related to the environment

CodePudding user response:

Dynamic - the 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 the loaded by specifying A full path, using DLL redirection, or by using A manifest. If none of these methods are 2, the system searches for A DLL at load time as described in this topic.

Standard Search Order
The dynamic - link library (DLL) search order 2 by The system depends on been 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, the create in registry key HKLM \ System \ CurrentControlSet \ Control \ the 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 The 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 The 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 the versions of Windows the prior to the ones listed at the beginning of this section do not support SafeDllSearchMode. For more information, see's Legacy Search Order below.

Alternate Search Order
The standard search order 2 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 and its behaviors continues until all associated executable modules have had 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:

nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull
  • Related