If you need a server to test, I can allocate an test instance for you. You can contact me by my register mail, and I will allocate an C5 instance in AWS for you.
My client asked to run my program on c5 series 's machine, which is a very urgent question
This is sure to be a bug in VMProtect, the source code is there for you, why not help debugging it?
I am a paying user, it is your responsibility to solve such bugs, and if you need the environment I can provide.
Looking forward to your reply
Please send an email to supermilg@qq.com with your email. I will send you the SSH login private key of the machine, and then you can operate the machine at will.
GDB also shows accessible memory region at 0x600ff8:
[centos@xxxx ~]$ gdb ./test_vmp
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-110.el7
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <> The GNU General Public License v3.0 - GNU Project - Free Software Foundation> >
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type “show copying”
and “show warranty” for details.
This GDB was configured as “x86_64-redhat-linux-gnu”.
For bug reporting instructions, please see:
<> Bugs in GDB> >…
Reading symbols from /home/centos/test_vmp…(no debugging symbols found)…done .
(gdb) r
Starting program: /home/centos/./test_vmp
Program received signal SIGSEGV, Segmentation fault.
0x00000000004003cc in ?? ()
Missing separate debuginfos, use: debuginfo-install glibc-2.17-222.el7.x86_64 li bgcc-4.8.5-28.el7_5.1.x86_64
(gdb) x/i 0x4003cc
=> 0x4003cc: mov 0x200c25(%rip),%rax # 0x600ff8
(gdb) x/g 0x600ff8
0x600ff8: 0
[centos@ip-172-31-2-223 ~]$ ./test
This is a test.
Test done.
test and test_vmp are the same program. The only difference is that test_vmp is protected by VMProtect.
If this is the BUG of CPU, test should not run. This is obviously the BUG of VMProtect. VMProtect is not compatible with this CPU.
Please help solve it, Thank you!
I tried a lot of machines, test_vmp can work properly, except for some machines.
Please login to the following server, test_vmp can run normally, you can compare and debug it.