src/lib/libc/stdio, branch release/8.1.0

MFC r204447:

2010-03-12T06:56:51Z

In _gettemp(), check that the length of the path doesn't exceed MAXPATHLEN. Otherwise the path name (or part of it) may not fit to carrybuf causing a buffer overflow. PR: bin/140228

MFC r197752:

2010-01-24T20:15:59Z

Better glibc compatibility for getline/getdelim: - Tolerate applications that pass a NULL pointer for the buffer and claim that the capacity of the buffer is nonzero. - If an application passes in a non-NULL buffer pointer and claims the buffer has zero capacity, we should free (well, realloc) it anyway. It could have been obtained from malloc(0), so failing to free it would be a small memory leak.

MFC r200802:

2010-01-20T00:53:44Z

Use vsprintf instead of rolling our own. PR: bin/140496 Submitted by: Jeremy Huddleston

MFC r200800:

2010-01-20T00:53:03Z

Use vsscanf instead of rolling our own. PR: bin/140530 Submitted by: Jeremy Huddleston

MFC r200799:

2010-01-20T00:52:24Z

K&R -> ANSI prototype.

MFC: r201836

2010-01-15T19:42:09Z

Remove unnecessary quoting and markup, add missing punctuation.

MFC: r200019

2009-12-07T08:38:44Z

Fix the dprintf() prototype.

MFC revs 199781,199782,199784,199785,199786:

2009-12-02T02:47:29Z

Eliminate dead stores. In __mbsconv(), if prec was zero, nconv could have been used uninitialized. Initialize it to a safe value so that there's no chance of returning an error if stack garbage happens to be equal to (size_t)-1 or (size_t)-2. In svc_raw_reply(), don't leave stat uninitialized if the MSG_ACCEPTED && SUCCESS case succeeds. The stack garbage might be zero. In clnt_raw_create(), avoid minor race condition initializing the file-scope variable clntraw_private. Found by: Clang static analyzer

Fix fwrite() to return 0 when size or nmemb are zero.

2009-07-12T13:09:43Z

Right now nmemb is returned when size is 0. In newer versions of the standards, it is explicitly required that fwrite() should return 0. Submitted by: Christoph Mallon Approved by: re (kib)

Return -1 instead of 0 upon reaching EOF. This is somewhat ill-advised

2009-04-06T13:50:04Z

because it means getdelim() returns -1 for both error and EOF, and never returns 0. However, this is what the original GNU implementation does, and POSIX inherited the bug. Reported by: marcus@