holycall holycall

Build with VS2015 x64 Native Tools Command Prompt. With 32bit Command Prompt, it fill fail with '... '_InterlockedIncrement64': identifier not found... ' errors.

I need to draw a huge graph requiring more than 4GB memory. Graphviz or D3JS cannot draw such huge graphs. Gephi is a good choice in this case. However Gephi visualization platform is run on 32bit Java by default. We need to change the configuration in order to run 64bit Java. In C:\Program Files (x86)\Gephi-0.9.1\etc\gephi.conf, deafult_options and jdkhome need to be modified. For example, defa..

I encountered following message box while I am using x64dbg + scyllahide. In the manual (ScyllaHide.pdf), it says that we need to download NtAPITool.rar and copy NtAPICollection.ini to x64\plugins folder.But the NtAPITool.rar does not fix this error. The OS minor version of the ini file is incorrect. So we need to fix the OS minor version. I am using Windows 8.1, so the OS minor version is 3. So..

I have the following errors after installing. Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directoryGtk-Message: Failed to load module "overlay-scrollbar": liboverlay-scrollbar.so: cannot open shared object file: No such file or directoryGtk-Message: Failed to load module "unity-gtk-module": libunity-gtk-modu..

The visual studio solution file in Intel Pin 3.0 needs to be fixed to build onVisual Studio 2015. The solution file at \pin\source\tools\MyPinTool is for Visual Studio 2010. It is converted to Visual Studio 2015 with warnings. The following file describes what is needed to build. https://software.intel.com/sites/default/files/managed/8e/f5/PinCRT.pdf The converted solution file already have most..

In visual studio command prompt, editbin /dynamicbase:no bin.exe

Visual Studio compiled programs use fastcall calling convention. Functions use RCX, RDX, R8, R9 first. After using them, functions use the stack. In variable argument functions such as printf, stack values are used.

With a faulty dump executable file, some conditional variables are defined although they are undefined in the real executable file. In such cases, hex-rays decomipler misunderstand the conditional expressions have constants and omit code chunks such that the decompiled function code contains small part of the original function. If we undefine the constants, then decompiler contains the ommited a..