On 5/8/17 2:33 PM, Eduardo Bustamante wrote:
> This doesn't seem to be related to the other read memory corruption
> issues, since it doesn't crash normal read/read -r.
Nope, it's the same.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis''
This doesn't seem to be related to the other read memory corruption
issues, since it doesn't crash normal read/read -r.
dualbus@afl-bash-history-fncm:~$ md5sum malloc
0edd8a721e52362d0aeeb30bae22c4f5 malloc
dualbus@afl-bash-history-fncm:~$ base64 malloc
/TAw/wHw8DAw8DAwMDAw8PD19fUw9fX19fX1MP9//P