bbqz007

constexpr in SafeInt3.hpp kills the compiling on vc2013

3

Release\include\cpprest\details\SafeInt3.hpp ```constexpr SafeInt(const SafeInt& u) SAFEINT_CPP_THROW = default;``` and i find ```CPPREST_CONSTEXPR``` by which cpprest solves the problem that vc120 does not fully support constexpr.

built by msys2 with gcc 10.2.0, usShell module crash and segment fault

3

``` MINGW64 ~ $ gcc --version gcc.exe (Rev6, Built by MSYS2 project) 10.2.0 ``` gdb usShell3 ``` (gdb) set args -llibusShellService0d.dll (gdb) r Starting program: \tmp\github\CppOSGi\build10\bin\usShell3.exe -llibusShellService0d.dll [New Thread 11684.0x15d8]...

when you see in the disassembly, you would find vc calls jump to the jmp tables why the calls can be hooked. a virtual method call in the vc disassemby...

`leal (%eax,%eax), %edx` invalid operand. failure parsing operand ` (%eax,%eax)`, bad supporting to index addressing

4

`leal (%eax,%eax), %edx` means `edx = eax + eax`,

keystone is bad supporting X86 when resolving PCRel.

1

``` // A number of ARM fixups in Thumb mode require that the effective PC // address be determined as the 32-bit aligned version of the actual offset. if (ShouldAlignPC)...

when the symbol contains '@', the sym_resolver failed to fire.

``` KEYSTONE_EXPORT ks_err ks_option(ks_engine *ks, ks_opt_type type, size_t value) { ks->MAI->setRadix(16); ``` it is freak that att style `12(%esp) ` is treated as 0x12 where 12 is not after `0x`

code generated by gcc ``` .align 4 _MessageBoxA: .long 19089016 LC0: .ascii "\0" push ebp mov ebp, esp sub esp, 24 mov eax, DWORD PTR _MessageBoxA mov ecx, OFFSET FLAT:LC0...

under ATT style, it treats decimal numbers as hexadecimal numbers. that is very painful.

1

code generated by gcc ``` .align 4 _MessageBoxA: .long 19089016 LC0: .ascii "\0" pushl %ebp movl %esp, %ebp subl $24, %esp movl _MessageBoxA, %eax movl $LC0, %ecx movl $LC0, %edx...

does this project port to python 3?

1

it seems that some functions are under the prototypes on python 2 .