On Fri, Sep 20, 2013 at 01:08:00PM -0700, Russ Allbery wrote: > So basically a variation of the old problem of calling memcpy when one > meant to use memmove. I'm actually surprised that type of call to sprintf > ever worked reliably with optimization, even without _FORTIFY_SOURCE. > But, like memcpy vs. memmove, it's the sort of thing that's horribly > difficult to debug.
This is something that can be tested for in s*printf() itself: deoptimizing it by a single comparison is probably worth catching a relatively popular error. -- ᛊᚨᚾᛁᛏᚣ᛫ᛁᛊ᛫ᚠᛟᚱ᛫ᚦᛖ᛫ᚹᛖᚨᚲ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130920220057.ga15...@angband.pl
