LOL! 

That must be for the folk that don't mind patching glibc, but will get
upset if memcpy does strange things. :)

On 7/23/05, Matt Randolph <[EMAIL PROTECTED]> wrote:
> Oh, and I take no responsibility for any damages to anyone or anything
> arising from the use of the revised memcpy.c or software produced from
> it.  It may contain further errors that I don't know about.
> 
> Matt Randolph wrote:
> 
> > There is a bug in the original memcpy.c that will cause a segfault if
> > you don't pass it any parameters.  Here is a fixed version.  I've left
> > everything else alone (except for a spelling correction).
> 
> 
> 
> --
> "Pluralitas non est ponenda sine necessitate" - W. of O.
> 
> --
> [email protected] mailing list
> 
>

-- 
[email protected] mailing list

Reply via email to