-
Notifications
You must be signed in to change notification settings - Fork 262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DrMemory 2.4 and 2.5 Unable to load client library on Windows Server 2008 R2 Enterprise #2440
Comments
As discussed in DynamoRIO/dynamorio#2658 please find out which DLL on your system exports MoveFileExW.
Xref https://groups.google.com/g/drmemory-users/c/V_43cs7Ys4I/m/qICdvPNSAgAJ Xref https://groups.google.com/g/dynamorio-users/c/2X4SYFrOMgk/m/qFFqLeSNBgAJ |
If your machine has |
Hi Derek, So I build drmemory-release_2.5.0 from source code with dynamorio-cronbuild-8.0.18915 sources without any changes in the code on my Windows 10 with VS 2017 (doesn't build with VS 2019).
When I launch DrMemory I got a system Error popup with following message: I looked on the net and found out that the first version of api-ms-win-downlevel-kernel32-l2-1-0.dll was released for the Windows 8.1 Operating System on 10/18/2013, while Windows Server 2008 R2 was released on July 22, 2009. On my Win 10 (WinVer=105;Rel=1909;Build=18363;Edition=Enterprise): I don't know if I'm doing something wrong. |
As requested above I was hoping you could provide confirmation that kernel32.dll exports I did get access to some Win7 libraries and we have:
I guess we just assume that matches 2008 R2. Re: other problems hit in #2440 (comment): I don't know; have not seen the first and the second would need a lot more information. I cannot reproduce them but again have no access to 2008 R2. In any case the import problem can be fixed. I would guess that it was never actually fixed in DynamoRIO/dynamorio#2658 and something else made it not matter. |
The exports are there in 6.2 == Win8 so it's just Win7:
|
Updates DR to 5e27a982 to fix DynamoRIO/dynamorio#2658 where Windows 7 has imports in kernel32.dll which are in kernelbase.dll on all subsequent Windows versions. Issue: #2440, DynamoRIO/dynamorio#2658
Describe the bug
When I use DrMemory 2.3 it work.
When I upgrade to 2.4 or 2.5, it fails with following message:
Unable to load client library: import MoveFileExW not found in KERNELBASE.dll.
I saw an issue that is now closed, where you had the same problem, but with previous version:
DynamoRIO/dynamorio#2658
To Reproduce
Steps to reproduce the behavior:
Pointer to a minimized application (ideally the source code for it and instructions on which toolchain it was built with).
I didn't try with a simple example, but I think it will fails with the same message.
Precise command line for running the application.
cd /d c:\dev\jenkins\workspace\qlib_diagnostics\Sources\qlibtester\projects & c:\dev\Dr.Memory\bin\drmemory.exe -logdir c:\dev\jenkins\workspace\qlib_diagnostics\qlib_5 -batch -brief -light -suppress c:\svn\Tools\trunk\Scripts..\drmemory-suppress.txt -- c:\dev\jenkins\workspace\qlib_diagnostics\Sources\qlibtester_exe32\qlibtester_vc19_q.exe -split 5/134 -selftest > c:\dev\jenkins\workspace\qlib_diagnostics\drmemory.qlib_5.win32.purify.drmemory.3.txt 2>&1
Exact output or incorrect behavior.
<Application c:\dev\jenkins\workspace\qlib_diagnostics\Sources\qlibtester_exe32\qlibtester_vc19_q.exe (8776). Unable to load client library: import MoveFileExW not found in KERNELBASE.dll.>
<Application c:\dev\jenkins\workspace\qlib_diagnostics\Sources\qlibtester_exe32\qlibtester_vc19_q.exe (8776). Unable to load client library: drmemorylib.dll: unable to process imports of client library..>
Dr.MWARNING: unable to locate results file: can't open c:\dev\jenkins\workspace\qlib_diagnostics\qlib_5/resfile.8776 (code=2).Dr. Memory failed to start the target application, perhaps due to
interference from invasive security software.
Try disabling other software or running in a virtual machine.
WARNING: Examine the following unusual libraries in this process to help identify
invasive software that may have affected the target application:
C:\Windows\system32\api-ms-win-core-localization-l1-2-0.dll
C:\Windows\system32\api-ms-win-core-file-l1-2-0.dll
C:\Windows\system32\api-ms-win-crt-time-l1-1-0.dll
C:\Windows\system32\api-ms-win-crt-runtime-l1-1-0.dll
C:\Windows\system32\api-ms-win-core-processthreads-l1-1-1.dll
C:\Windows\system32\api-ms-win-core-timezone-l1-1-0.dll
C:\Windows\system32\api-ms-win-crt-string-l1-1-0.dll
C:\Windows\system32\api-ms-win-core-file-l2-1-0.dll
C:\Windows\system32\api-ms-win-crt-locale-l1-1-0.dll
C:\Windows\system32\api-ms-win-crt-private-l1-1-0.dll
C:\Windows\system32\api-ms-win-core-synch-l1-2-0.dll
Please file a bug about this at http://drmemory.org/issues
Dr.MWARNING: application exited with abnormal code 0xffffffffPlease also answer these questions drawn from https://drmemory.org/page_help.html#sec_narrow :
-light
to Dr. Memory)?No
-leaks_only -no_count_leaks -no_track_allocs
?Didn't try
dynamorio/bin32/drrun -- <application and args>
ordynamorio/bin64/drrun -- <application and args>
depending on the bitwidth of your applicaiton. (Ignore warnings about "incomplete installation".)Yes Application runs well
-debug -dr_debug -pause_at_assert
. Are any messages reported?Didn't try
Expected behavior
DrMemory to run as with version 2.3
Versions
What version of Dr. Memory are you using?
DrMemory-Windows-2.4.0-2.msi and DrMemory-Windows-2.5.0.msi
Does the latest build from
https://drmemory.org/page_download.html#sec_latest_build solve the problem?
No with DrMemory-Windows-2.5.18954.msi. DrMemory-Windows-2.3.0-1.msi is the last version where it works
What operating system version are you running on? ("Windows 10" is not sufficient: give the release number.)
OS Name: Microsoft Windows Server 2008 R2 Enterprise
OS Version: 6.1.7601 Service Pack 1 Build 7601
OS Build Type: Multiprocessor Free
System Model: Virtual Machine
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 85 Stepping 4 GenuineIntel ~2095 Mhz
BIOS Version: American Megatrends Inc. 090006 , 28/04/2016
Is your application 32-bit or 64-bit?
32-bit
The text was updated successfully, but these errors were encountered: