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
feli-citas opened this issue
Aug 26, 2019
· 1 comment
Assignees
Labels
area-vmUse area-vm for VM related issues, including code coverage, and the AOT and JIT backends.dartfuzzFound with Dart fuzzing (DartFuzz, libFuzzer, etc.)
The text was updated successfully, but these errors were encountered:
feli-citas
added
area-vm
Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends.
dartfuzz
Found with Dart fuzzing (DartFuzz, libFuzzer, etc.)
labels
Aug 26, 2019
Ah, Dart int-s are always 64-bit. However, intptr_t-s are architecture dependent. So this behavior is to be expected. Let's not call C++ functions that depend on intptr_t.
area-vmUse area-vm for VM related issues, including code coverage, and the AOT and JIT backends.dartfuzzFound with Dart fuzzing (DartFuzz, libFuzzer, etc.)
32 bit Integer overflows lead to divergence between 32 and 64 bit dart versions when parameter is passed through an FFI intptr_t.
64 bit
32 bit
The text was updated successfully, but these errors were encountered: