On Fri, Sep 04, 2009 at 12:16:56PM +0200, R??mi Denis-Courmont wrote: > To me, this looks like it's working around a bug somewhere else, which > is bad. Could be. No idea where then, though. On the upside this does avoid an avoidable memcpy() so it's not all bad.