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
On my box the hash functions cause core dumps. Here's why..
compilers from version to version will compile structures differently, and some types the size of a 'size_t' type might be 4 or 8 bytes.. On my box the
I think you have it as 357 or something (hardcoded in python).. python gets very unhappy and core dumps. boo.
I'm not that familiar with ctypes (and sorry you switched from FFI), so I'm not sure if there is a nice way to find the size programmatically. if so use that.. otherwise, making it 361 won't hurt (will just waste a few bytes of space otherwise).
thanks again!
nickg
The text was updated successfully, but these errors were encountered:
Hey thanks for starting this!
On my box the hash functions cause core dumps. Here's why..
compilers from version to version will compile structures differently, and some types the size of a 'size_t' type might be 4 or 8 bytes.. On my box the
printf("%d\n", sizeof(struct crypto_generichash_blake2b_state));
is 361
I think you have it as 357 or something (hardcoded in python).. python gets very unhappy and core dumps. boo.
I'm not that familiar with ctypes (and sorry you switched from FFI), so I'm not sure if there is a nice way to find the size programmatically. if so use that.. otherwise, making it 361 won't hurt (will just waste a few bytes of space otherwise).
thanks again!
nickg
The text was updated successfully, but these errors were encountered: