-
Notifications
You must be signed in to change notification settings - Fork 69
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
Building error with DynamoRIO on Windows 10 64bits #30
Comments
I was trying to build DRLtrace for Windows 64bits, using the versions of the required software listed in the how to build section of Windows, and I got this issue :
I am using VS 2013, CMake 3.2 and Starwberry Perl 5.32.1.1 64bit. Can you help me figure out the issue?
|
Hi, thanks for your interest in drltrace. Are you compiling using |
Hi! I have the same output with all types of terminal, Powershell, cmd, or using the Developer Command Prompt for VS2013 x64 from VS 2013 tools. |
Nevermind, sorry. I forgot to clear the CMake cache files. |
What do you mean by nothing new? Is the log file empty? |
No, it contains a lot of calls, but all of these were written before the calculator window showed up, and there was nothing more afterwards. Here is the end of the log file:
|
Just realized this one is from explorer.exe, but it is exactly the same issue. |
Yes, it is a common problem when you trace standard applications on Windows 10 if I recall it correctly. You could try to run some third-party app and check results. |
Well I have another problem with other apps...When I just launch them normally with Powershell, from the app's directory, without launching DRLtrace, they start normally, but when I use DRLtrace, they won't start, there is just : "INFO: <.exe path> successfully started, waiting app for exit" and it returns one second later, with no app showing up... |
Maybe I should create another issue? |
Yes, please create a new one and share executable that you run along with details on drltrace version and DR engine. |
No description provided.
The text was updated successfully, but these errors were encountered: