Closed mitchcurtis closed 6 years ago
The Heob executables must be in the appropriate location.
This means it didn't find the heob executable in the directory you set. If you run heob with a 64bit program, then you need the heob64.exe.
The problem could be that the x64 binaries aren't built? I'm using the x64 command prompt.
Yes, looks like you're right about that. If you used the x64 command prompt, then heob64.exe should have been built, not heob32.exe. Seems the detection of 32/64 bit doesn't work for you, it is very simple:
echo %lib% |find /i "lib\amd64" >NUL
if errorlevel 1 (
set bits=32
) else (
set bits=64
)
And in your case %lib% has this:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\ATLMFC\lib\x64;C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.11.25503\lib\x64;C:\Program Files (x86)\Windows Kits\10\lib\10.0.15063.0\ucrt\x64;C:\Program Files (x86)\Windows Kits\10\lib\10.0.15063.0\um\x64
There is no lib\amd64
, only lib\x64
.
I've so far only used MSVC 2015, and in 2017 this seems to have changed.
So maybe just change it to echo %lib% |find /i "lib\x64" >NUL
and try again.
Thanks, changing it to that fixes it.
What's weird is that even using the self-built one, I don't get the option to debug the heob when it crashes. Is it not using debug information?
No, it's not. I don't need to debug heob often lately, and if I do, I usually use gcc/gdb.
You get debug information with build.bat if you add /Zi
to CFLAGS, and /DEBUG
to LDFLAGS.
Oops, I didn't mean to close this one, pushed the wrong button.
Since you were able to use your self-built heob, and no new questions came up, I'm closing this now.
I'm trying to run a self-built heob in Qt Creator, but get the following error message:
This is the build output from build.bat on a Windows 10 machine:
I get the following build artifacts:
The problem could be that the x64 binaries aren't built? I'm using the x64 command prompt.