search

codecat / ClawSearch

A memory scanner plugin for x64dbg, inspired by Cheat Engine.
GNU General Public License v3.0
274 stars 40 forks source link

Compiled release of the plugin #4

Closed prolium closed 6 years ago

prolium commented 6 years ago

Hello, first I would like to point out that this is not a bug report, but rather a request. For quite some time I've wanted to use your plugin, but I don't have VS2015 and compiling it on VS2013 is painful, throws many linking issues as in issue #3 .

Could you please release a compiled package of the plugin occasionally ?

codecat commented 6 years ago

Sure, I'll take a look late tonight.

codecat commented 6 years ago

Hey, I've uploaded prebuilt binaries here. Let me know if they work, I haven't had much time to try it yet today.

I've also fixed a few building errors and committed those, so if you want to compile it yourself, maybe it will work now.

prolium commented 6 years ago

Thanks a lot, the 32-bit version worked (tested on Sonic Mania), but the 64-bit version didn't, log tab says failed to load plugin.

As for compiling the project, i found that the linking problem was because of the libraries IUP and CD since they're built with static linking to Visual C++ 14.0 (2015) as stated here in the download tips page. After replacing all .lib files of IUP and CD with the ones built for Visual C++ 12.0 (2013) , the project was successfully compiled!

But comes another problem, if the plugin was compiled with the static version of both libraries, then the 64-bit version fails to be loaded in the debugger, but if the project was built with the dynamic version of the libraries then it works! but then of course you have to copy/paste the .dll files along the with the .dp64 file.

Debugger version: snapshot_2017-10-24_01-20 OS: Windows 10 x64 v1607 (build 14393, aka Anniversary Update )

codecat commented 6 years ago

That's interesting. I don't really understand why that would be a problem. Maybe it's linking with the wrong static lib files or something?

Since this issue is solved, I'll close it now. Perhaps open a new issue for the static libs?

prolium commented 6 years ago

Sure, will do, i'll try to figure out what's wrong (if i could) before opening a new issue.