@mkf@dan bug or misuse. Memcpy() is explicitly documented to have undefined behaviour if copied regions overlap. You need memmove() if that is the case. I'd be truly astonished if a bug in memcpy() laid undiscovered for any length of time. Literally everything would be broken.
@briancs@dan that is a good basis for presuming my memory may wrong me, wouldn't be a rare occurence. i will sometime see back in my fedi boosts to find the thing i may have had misread and come back with it
Gregory's Server
@mkf @dan bug or misuse. Memcpy() is explicitly documented to have undefined behaviour if copied regions overlap. You need memmove() if that is the case. I'd be truly astonished if a bug in memcpy() laid undiscovered for any length of time. Literally everything would be broken.