cmake | ||
tests | ||
.editorconfig | ||
.gitattributes | ||
.travis.yml | ||
appveyor.yml | ||
CMakeLists.txt | ||
README.md | ||
subhook_private.h | ||
subhook_unix.c | ||
subhook_windows.c | ||
subhook_x86.c | ||
subhook.c | ||
subhook.h |
SubHook is a super-simple hooking library for C and C++ that works on Windows, Linux and macOS. It supports x86 only (32-bit and 64-bit).
Installation
Simply copy the files to your project and include subhook.c in your build.
The other source files wil be #included
by the main C file automatically
depending on the OS and achitecture.
Use of CMake is not mandatory, the library can be built wihtout it (no extra build configuration required).
Examples
In the following examples foo
is some function or a function pointer that
takes a single argument of type int
and uses the same calling convention
as my_foo
(depends on compiler).
Basic usage
#include <stdio.h>
#include <subhook.h>
subhook_t foo_hook;
void my_foo(int x) {
/* Remove the hook so that you can call the original function. */
subhook_remove(foo_hook);
printf("foo(%d) called\n", x);
foo(x);
/* Install the hook back to intercept further calls. */
subhook_install(foo_hook);
}
int main() {
/* Create a hook that will redirect all foo() calls to to my_foo(). */
foo_hook = subhook_new((void *)foo, (void *)my_foo, 0);
/* Install it. */
subhook_install(foo_hook);
foo(123);
/* Remove the hook and free memory when you're done. */
subhook_remove(foo_hook);
subhook_free(foo_hook);
}
Trampolines
Using trampolines allows you to jump to the original code without removing and re-installing hooks every time your function gets called.
typedef void (*foo_func)(int x);
void my_foo(int x) {
printf("foo(%d) called\n", x);
/* Call foo() via trampoline. */
((foo_func)subhook_get_trampoline(foo_hook))(x);
}
int main() {
/* Same code as in previous example. */
}
Please note that subhook has a very simple length disassmebler engine (LDE) that works only with most common prologue instructions like push, mov, call, etc. When it encounters an unknown instruction subhook_get_trampoline() will return NULL.
C++
#include <iostream>
#include <subhook.h>
subhook::Hook foo_hook;
subhook::Hook foo_hook_tr;
typedef void (*foo_func)(int x);
void my_foo(int x) {
// ScopedHookRemove removes the specified hook and automatically re-installs
// it when the objectt goes out of scope (thanks to C++ destructors).
subhook::ScopedHookRemove remove(&foo_hook);
std::cout << "foo(" << x << ") called" << std::endl;
foo(x + 1);
}
void my_foo_tr(int x) {
std::cout << "foo(" << x << ") called" << std::endl;
// Call the original function via trampoline.
((foo_func)foo_hook_tr.GetTrampoline())(x + 1);
}
int main() {
foo_hook.Install((void *)foo, (void *)my_foo);
foo_hook_tr.Install((void *)foo, (void *)my_foo_tr);
}
Known issues
-
subhook_get_trampoline()
may return NULL because only a small subset of x86 instructions is supported by the disassembler in this library (only common prologue instructions). As a workaround you can plug in a more advanced disassembler engine insubhook_disasm()
(currently there is no simple way to do it, you have to modify the code manually). -
If a target function (the function you are hooking) is less than N bytes in length, for example if it's a short 2-byte jump to a nearby location (sometimes compilers generate code like this), then you will not be able to hook it.
N is 5 by default: 1 byte for jmp opcode + 4 bytes for offset. But if you enable the use of 64-bit offsets in 64-bit mode N becomes 14 (see the definition of
subhook_jmp64
). -
Some systems protect executable code form being modified at runtime, which will not allow you to install hooks, or don't allow to mark heap-allocated memory as executable, which prevents the use of trampolines.
For example, on Fedora you can have such problems because of SELinux (though you can disable it or exclude your files).
License
Licensed under the 2-clause BSD license.