[physfs] Possible mem corruption in 2.0.2 or just my bad?
Ryan C. Gordon
icculus at icculus.org
Tue Jul 5 20:46:56 EDT 2011
> here Valgrind starts to complain:
> ==18794== Source and destination overlap in memcpy(0x9ad090b, 0x9ad090a, 9)
> ==18794== at 0x4C27B46: memcpy (in /usr/lib/valgrind/vgpreload_memcheck-
> ==18794== by 0x5D759C4: ??? (in /lib/libc-2.14.so)
> ==18794== by 0x5D75386: readdir (in /lib/libc-2.14.so)
This looks like a minor bug in libc, not your code or PhysicsFS.
More information about the physfs