You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using gcc (4.8.2) and clang (3.3 or 3.6) ripe_attack_generator.c fails to compile:
Here are two errors I've seen a few times:
/source/ripe_attack_generator.c:80:34: error: initializer element is not a
compile-time constant
0xDEADBEEF,0xDEADBEEF,0xDEADBEEF,&exit, &cf_ret_param,448}; //448 => 0700 mode
^~~~~
./source/ripe_attack_generator.c:112:27: error: initializer element is not a
compile-time constant
static int rop_sled[7] = {&gadget1 + 62,0xFFFFFFFF,&gadget2 + 62,&cf_ret...
^~~~~~~~~~~~~
Any idea what it would take to fix this? From a cursory look at the file, it looks like these could just be filled in at runtime...
The text was updated successfully, but these errors were encountered:
This issue seems not effecting 32-bit builds. I faced the same issue exactly as @jugonz described, but it disappeared after passing '-m32' to GCC (5.2.0) or Clang (3.6.2).
Using gcc (4.8.2) and clang (3.3 or 3.6) ripe_attack_generator.c fails to compile:
Here are two errors I've seen a few times:
/source/ripe_attack_generator.c:80:34: error: initializer element is not a
compile-time constant
0xDEADBEEF,0xDEADBEEF,0xDEADBEEF,&exit, &cf_ret_param,448}; //448 => 0700 mode
^~~~~
./source/ripe_attack_generator.c:112:27: error: initializer element is not a
compile-time constant
static int rop_sled[7] = {&gadget1 + 62,0xFFFFFFFF,&gadget2 + 62,&cf_ret...
^~~~~~~~~~~~~
Any idea what it would take to fix this? From a cursory look at the file, it looks like these could just be filled in at runtime...
The text was updated successfully, but these errors were encountered: