VTIL-Core
VTIL-Core copied to clipboard
Virtual-machine Translation Intermediate Language
Is it possible to add support for x32_86 architecture?
https://github.com/vtil-project/VTIL-Core/blob/7e741095abbe571a9feddb09066fe13109d204a7/VTIL-Architecture/trace/tracer.cpp#L504-L507 ... https://github.com/vtil-project/VTIL-Core/blob/7e741095abbe571a9feddb09066fe13109d204a7/VTIL-Architecture/trace/tracer.cpp#L526-L529 lvm.execute can do read_register: https://github.com/vtil-project/VTIL-Core/blob/7e741095abbe571a9feddb09066fe13109d204a7/VTIL-Architecture/vm/interface.cpp#L45-L51 read_register in turn calls tracer: https://github.com/vtil-project/VTIL-Core/blob/7e741095abbe571a9feddb09066fe13109d204a7/VTIL-Architecture/vm/lambda.hpp#L66-L71 And se we end up with a stack overflow.
The following code is producing corrupt results: ```C++ void run_err_test_1() { auto b = vtil::basic_block::begin(0); auto first = vtil::register_desc(vtil::register_flag::register_local, 0, 64); auto second_ptr = vtil::register_desc(vtil::register_flag::register_local, 5, 64); auto second =...
It is required for std::exchange() on GCC. Some other compilers include it automatically (maybe for ``?) See: https://en.cppreference.com/w/cpp/utility#Swap See also this issue: https://github.com/doxygen/doxygen/issues/9312
Hello. ```cpp DOCTEST_TEST_CASE("dummy") { vtil::logger::log("\n\n>> %s \n", __FUNCTION__); auto block = vtil::basic_block::begin(0); auto [t0, t1, t2, t3] = block->tmp(64, 64, 1, 64); auto rtn = block->owner; block->mov(t0, vtil::REG_FLAGS); block->bnot(t0); block->ifs(t1,...
bug ```cpp auto block = vtil::basic_block::begin(0x1337); vtil::register_desc reg_ecx(vtil::register_physical, registers::cx, vtil::arch::bit_count, 0); auto sr0 = block->owner->alloc(vtil::arch::bit_count); // The ecx register here is a potential function argument, register_renaming_pass should not work here....
 Here it is without the annoying function_view stuff obscuring the call stack:  I will update the issue with more information and code snippets as I acquire...