Revision tags: release/5.1.0_cvs, release/5.1.0, release/4.8.0_cvs, release/4.8.0, release/5.0.0_cvs, release/5.0.0, release/4.7.0_cvs |
|
#
48eaac24 |
| 17-Sep-2002 |
Maxim Konovalov <maxim@FreeBSD.org> |
Fix vsnprintf(3) memory leak for size == 0.
PR: bin/36175 Obtained from: OpenBSD Reviewed by: silence on -audit MFC after: 5 days
|
#
58d38e25 |
| 06-Sep-2002 |
Tim J. Robbins <tjr@FreeBSD.org> |
Style: One space between "restrict" qualifier and "*".
|
#
abbd8902 |
| 21-Aug-2002 |
Mike Barcroft <mike@FreeBSD.org> |
o Merge <machine/ansi.h> and <machine/types.h> into a new header called <machine/_types.h>. o <machine/ansi.h> will continue to live so it can define MD clock macros, which are only MD because of
o Merge <machine/ansi.h> and <machine/types.h> into a new header called <machine/_types.h>. o <machine/ansi.h> will continue to live so it can define MD clock macros, which are only MD because of gratuitous differences between architectures. o Change all headers to make use of this. This mainly involves changing: #ifdef _BSD_FOO_T_ typedef _BSD_FOO_T_ foo_t; #undef _BSD_FOO_T_ #endif to: #ifndef _FOO_T_DECLARED typedef __foo_t foo_t; #define _FOO_T_DECLARED #endif
Concept by: bde Reviewed by: jake, obrien
show more ...
|
#
f8418db7 |
| 15-Aug-2002 |
Robert Drehmel <robert@FreeBSD.org> |
- For compliance with IEEE Std 1003.1-2001, add the 'restrict' qualifier to function prototypes and definitions where appropriate using the '__restrict' macro. - Update the manual page.
|
Revision tags: release/4.6.2_cvs, release/4.6.2 |
|
#
e74101e4 |
| 13-Aug-2002 |
Tim J. Robbins <tjr@FreeBSD.org> |
Basic support for wide character I/O: getwc(), fgetwc(), getwchar(), putwc(), fputwc(), putwchar(), ungetwc(), fwide().
|
Revision tags: release/4.6.1, release/4.6.0_cvs |
|
#
333fc21e |
| 22-Mar-2002 |
David E. O'Brien <obrien@FreeBSD.org> |
Fix the style of the SCM ID's. I believe have made all of libc .c's as consistent as possible.
|
Revision tags: release/4.5.0_cvs, release/4.4.0_cvs |
|
#
a52532c9 |
| 18-Jun-2001 |
Assar Westerlund <assar@FreeBSD.org> |
revert freeing of memory that gets allocated when str == NULL (this will be fixed in a better way)
PR: misc/26044
|
#
207d92d0 |
| 16-Jun-2001 |
Assar Westerlund <assar@FreeBSD.org> |
free memory that gets allocated by vfprintf when str == NULL
PR: misc/26044
MFC after: 1 week
|
Revision tags: release/4.3.0_cvs, release/4.3.0 |
|
#
d201fe46 |
| 24-Jan-2001 |
Daniel Eischen <deischen@FreeBSD.org> |
Remove _THREAD_SAFE and make libc thread-safe by default by adding (weak definitions to) stubs for some of the pthread functions. If the threads library is linked in, the real pthread functions will
Remove _THREAD_SAFE and make libc thread-safe by default by adding (weak definitions to) stubs for some of the pthread functions. If the threads library is linked in, the real pthread functions will pulled in.
Use the following convention for system calls wrapped by the threads library: __sys_foo - actual system call _foo - weak definition to __sys_foo foo - weak definition to __sys_foo
Change all libc uses of system calls wrapped by the threads library from foo to _foo. In order to define the prototypes for _foo(), we introduce namespace.h and un-namespace.h (suggested by bde). All files that need to reference these system calls, should include namespace.h before any standard includes, then include un-namespace.h after the standard includes and before any local includes. <db.h> is an exception and shouldn't be included in between namespace.h and un-namespace.h namespace.h will define foo to _foo, and un-namespace.h will undefine foo.
Try to eliminate some of the recursive calls to MT-safe functions in libc/stdio in preparation for adding a mutex to FILE. We have recursive mutexes, but would like to avoid using them if possible.
Remove uneeded includes of <errno.h> from a few files.
Add $FreeBSD$ to a few files in order to pass commitprep.
Approved by: -arch
show more ...
|
Revision tags: release/4.2.0, release/4.1.1_cvs, release/4.1.0, release/3.5.0_cvs, release/4.0.0_cvs, release/3.4.0_cvs, release/3.3.0_cvs |
|
#
7f3dea24 |
| 28-Aug-1999 |
Peter Wemm <peter@FreeBSD.org> |
$Id$ -> $FreeBSD$
|
Revision tags: release/3.2.0, release/3.1.0, release/3.0.0, release/2.2.8, release/2.2.7, release/2.2.6 |
|
#
8c6d2f42 |
| 01-Jan-1998 |
Andrey A. Chernov <ache@FreeBSD.org> |
1. EOF was returned when the buffer size was larger than INT_MAX. This case has very little to do with the output size being larger than INT_MAX. 2. The new #include of <limits.h> was disorder
1. EOF was returned when the buffer size was larger than INT_MAX. This case has very little to do with the output size being larger than INT_MAX. 2. The new #include of <limits.h> was disordered. 3. The new declaration of `on' was disordered (integer types go together). 4. Testing an unsigned value for > 0 was fishy.
Submitted by: bde
show more ...
|
#
fb25537f |
| 25-Dec-1997 |
Andrey A. Chernov <ache@FreeBSD.org> |
Correct type of stored argument place (from previous fix)
|
#
6e690ad4 |
| 25-Dec-1997 |
Andrey A. Chernov <ache@FreeBSD.org> |
Return back to BSD snprintf semantics which recent C9x standard adopts instead of Singe Unix, thanx Bruce for explaining, I am not realize standards war was there.
But now, fix n == 0 case to not re
Return back to BSD snprintf semantics which recent C9x standard adopts instead of Singe Unix, thanx Bruce for explaining, I am not realize standards war was there.
But now, fix n == 0 case to not return error and fix check for too big n.
Things left to do: check for overflow in arguments.
show more ...
|
#
e0b123f6 |
| 24-Dec-1997 |
Andrey A. Chernov <ache@FreeBSD.org> |
1) Oops! Insert again if (n == 0) return 0.
Final word is Bruce's quote:
C9x specifies the BSD4.4-Lite behaviour:
[#3] ... Thus, the null-terminated output has been completely
1) Oops! Insert again if (n == 0) return 0.
Final word is Bruce's quote:
C9x specifies the BSD4.4-Lite behaviour:
[#3] ... Thus, the null-terminated output has been completely written if and only if the returned value is less than n.
It means that if we not have any null-terminated output as for n == 0 we can't return value less than n, so we forced to return value equal to n i.e. 0
The next good thing is glibc compatibility, of course.
2) Do check for too big n in machine-independent way. 3) Minor optimization assuming EOF is < 0
show more ...
|
#
5ebfa8de |
| 24-Dec-1997 |
Andrey A. Chernov <ache@FreeBSD.org> |
Back out part related to "return 0 if n == 0" and return EOF as before.
The main argument is that it is impossible to determine if %n evaluated or not when snprintf return 0, because it can happens
Back out part related to "return 0 if n == 0" and return EOF as before.
The main argument is that it is impossible to determine if %n evaluated or not when snprintf return 0, because it can happens for both n == 0 and n == 1. Although EOF here is good indication of the end of process, if n is decreased in the loop... Since it is already supposed in many places that EOF *is* negative, f.e. from Single Unix specs for snprintf "return ... a negative value if an output error was encountered" this not makes situation worse.
show more ...
|
#
4ecaf220 |
| 24-Dec-1997 |
Andrey A. Chernov <ache@FreeBSD.org> |
snprintf return value fixes to conform Single Unix specs:
1) if buffer size is smaller than arguments size, return buffer size, not arguments size as before.
2) if buffer size is 0, return 0, not E
snprintf return value fixes to conform Single Unix specs:
1) if buffer size is smaller than arguments size, return buffer size, not arguments size as before.
2) if buffer size is 0, return 0, not EOF as before. (now it is compatible with Linux and Apache implementations too).
NOTE: Single Unix specs says:
If the value of n {buffer size} is zero on a call to snprintf(), an unspecified value less than 1 is returned.
It means we can't return EOF since EOF can take *any* value in general not especially < 1. Better variant will be return -1 (it is less then 1 and different with n == 1 case) but -1 value is already occuped by EOF in our implementation, so we can't distinguish true IO error in that case. So 0 here is only possible case still conforming to Single Unix specs.
show more ...
|
Revision tags: release/2.2.5_cvs, release/2.2.2_cvs, release/2.2.1_cvs, release/2.2.0, release/2.1.7_cvs |
|
#
7e546392 |
| 22-Feb-1997 |
Peter Wemm <peter@FreeBSD.org> |
Revert $FreeBSD$ to $Id$
|
Revision tags: release/2.1.6_cvs, release/2.1.6.1 |
|
#
1130b656 |
| 14-Jan-1997 |
Jordan K. Hubbard <jkh@FreeBSD.org> |
Make the long-awaited change from $Id$ to $FreeBSD$
This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so
Make the long-awaited change from $Id$ to $FreeBSD$
This will make a number of things easier in the future, as well as (finally!) avoiding the Id-smashing problem which has plagued developers for so long.
Boy, I'm glad we're not using sup anymore. This update would have been insane otherwise.
show more ...
|
Revision tags: release/2.1.5_cvs |
|
#
ce51cf03 |
| 22-Jun-1996 |
James Raynard <jraynard@FreeBSD.org> |
Suggested by: Bruce Evans, Jeffrey Hsu, Gary Palmer
Added $Id$'s to files that were lacking them (gpalmer), made some cosmetic changes to conform to style guidelines (bde) and checked against NetBSD
Suggested by: Bruce Evans, Jeffrey Hsu, Gary Palmer
Added $Id$'s to files that were lacking them (gpalmer), made some cosmetic changes to conform to style guidelines (bde) and checked against NetBSD and Lite2 to remove unnecessary divergences (hsu, bde)
One last code cleanup:-
Removed spurious casts in fseek.c and stdio.c. Added missing function argument in fwalk.c. Added missing header include in flags.c and rget.c. Put in casts where int's were being passed as size_t's. Put in missing prototypes for static functions. Changed second args of __sflags() inflags.c and writehook() in vasprintf.c from char * to const char * to conform to prototypes.
This directory now compiles with no warnings with -Wall under gcc-2.6.3 and with considerably less warnings than before with the ultra-pedantic script I used for testing. (Most of the remaining ones are due to const poisoning).
show more ...
|
#
f70177e7 |
| 22-Jan-1996 |
Julian Elischer <julian@FreeBSD.org> |
Reviewed by: julian and (hsu?) Submitted by: John Birrel(L?)
changes for threadsafe operations
|
Revision tags: release/2.1.0_cvs, release/2.0.5_cvs, release/2.0, release/1.1.5.1_cvs |
|
#
58f0484f |
| 27-May-1994 |
Rodney W. Grimes <rgrimes@FreeBSD.org> |
BSD 4.4 Lite Lib Sources
|