ok, with newer libc's overlapping memcpys will fail:
http://article.gmane.org/gmane.comp.lib.glibc.alpha/15278
I'm pretty shure we had some of them, now they might fall on our feet.
Push to the project citadel.org : The branch, master has been updated
via a629da83391d58813cc962f6c52d991868b10e3a (commit)
via 0b543f0266b19d4654406dc00f652bed445f624c (commit)
via 1bca8e52ac5e6713c26867195fffed2e49861f0e (commit)
via
Sun Nov 14 2010 17:16:49 EST from "dothebart" dotheb...@uncensored.citadel.org Subject: [SCM] citadel.org branch, master, updated. a629da83391d58813cc962f6c52d991868b10e3a
http://code.citadel.org/cgit.cgi/git.citadel.org/commit/?id=1bca8e52ac5e6713c26867195fffed2e49861f0e commit
IG, could you have a look at this? why does the mentioned pointer
contain invalid data instead of NULL? could you clean that up?
Which pointer are we talking about here?
Push to the project citadel.org : The branch, master has been updated
via 2993a1dc1eb0a043c3ebeff83cf6f9cfad8adb93 (commit)
from a629da83391d58813cc962f6c52d991868b10e3a (commit)
Those revisions listed above that are new to this repository have not appeared
on any other
