kre 63e182f423 snprintb(3) says that, in the new(?) Torek format, all fields specs end with \0 ... The F spec is one of those, it should be terminated with \0 just like all the others (irrelevant that it has no extra data to delimit). Fix <sys/mman.h> to define the snprintb() format string correctly (include the missing \0's). Fix the copy of that definition included into snprintb(3) to match the updated mman.h version (ride the date bump from the day before yesterday .. this is the same change, just corrected). Undo the previous snprintb.c change ("off by one" fix) which was an attempt to make the broken mman.h usage work (and did, but not the way it should be done). Also, after using the new * format (instead of only when something has already matched) skip the associated data so we don't attempt to interpret it as more field specifiers. This func needs lots of TLC! Fix the ATF tests for snprintb() to not assume that F format is really exactly like f format, and has data after the field specifier. It doesn't. Add several more tests (including testing the '*' field operator recently added).		2019-04-29 07:55:38 +00:00
..
Makefile	Add some naive tests for the efun(3) family of debug functions.	2011-03-30 17:02:17 +00:00
t_efun.c	add missing includes	2012-11-04 23:37:02 +00:00
t_parsedate.c	Fix typo in a comment.	2017-03-22 05:35:33 +00:00
t_pidfile.c	Extend pidfile(3) to support creating pid files in arbitrary locations.	2011-03-29 13:55:37 +00:00
t_snprintb.c	snprintb(3) says that, in the new(?) Torek format, all fields specs end with \0	2019-04-29 07:55:38 +00:00
t_sockaddr_snprintf.c	…