[physfs] Possible mem corruption in 2.0.2 or just my bad?
Christian
zicodxx at yahoo.de
Thu Jul 14 19:45:46 EDT 2011
Hey Ryan,
Thanks for your reply. Actually, after posting my message I found a similar
report from way back in 2005 (I think). I should have searched that before but
the fact a user reported an actual crash with a similar backtrace at the same
point made me a bit confused. As it may be - thanks again. :)
Regards,
Christian
On Tuesday, July 05, 2011 20:46:56 Ryan C. Gordon wrote:
> > 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- amd64-linux.so)
> > ==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.
>
> --ryan.
>
> _______________________________________________
> physfs mailing list
> physfs at icculus.org
> http://icculus.org/mailman/listinfo/physfs
--
http://www.dxx-rebirth.com // The Rebirth of Descent
Lead Programmer, Project Maintainer
More information about the physfs
mailing list