#
9b4dadd3 |
| 03-Apr-2009 |
Xin LI <delphij@FreeBSD.org> |
Properly handle malloc() failures.
PR: bin/83338
|
Revision tags: release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0, release/7.0.0_cvs, release/7.0.0, release/6.3.0_cvs, release/6.3.0, release/6.2.0_cvs, release/6.2.0 |
|
#
c879ae35 |
| 09-Jan-2007 |
Warner Losh <imp@FreeBSD.org> |
Per Regents of the University of Calfornia letter, remove advertising clause.
# If I've done so improperly on a file, please let me know.
|
Revision tags: release/5.5.0_cvs, release/5.5.0, release/6.1.0_cvs, release/6.1.0, release/6.0.0_cvs, release/6.0.0, release/5.4.0_cvs, release/5.4.0, release/4.11.0_cvs, release/4.11.0, release/5.3.0_cvs, release/5.3.0, release/4.10.0_cvs, release/4.10.0, release/5.2.1_cvs, release/5.2.1, release/5.2.0_cvs, release/5.2.0, release/4.9.0_cvs, release/4.9.0, 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 |
|
#
464ef179 |
| 02-Jan-2003 |
Thomas Quinot <thomas@FreeBSD.org> |
In cgetmatch(3), return -1 if a NULL or 0-length name parameter is used. This situation most notably arises in chkprintcap, when a /etc/printcap entry has an empty rp= attribute. In that case, cgetma
In cgetmatch(3), return -1 if a NULL or 0-length name parameter is used. This situation most notably arises in chkprintcap, when a /etc/printcap entry has an empty rp= attribute. In that case, cgetmatch would enter an infinite loop if any entry in the file has multiple names.
This causes lpd to hang at boot time on 5.0-DP2 when both conditions are met (:rp=: and multiple names -- not necessarily on the same entry).
Reviewed by: roberto
show more ...
|
#
beb24986 |
| 27-Dec-2002 |
Alfred Perlstein <alfred@FreeBSD.org> |
Silence casting away constness warnings.
Make cgetmatch's locals const. Make cdbget take a const string and copy it into a buffer.
|
Revision tags: release/4.7.0_cvs, release/4.6.2_cvs, release/4.6.2, release/4.6.1, release/4.6.0_cvs |
|
#
1372519b |
| 22-Mar-2002 |
David E. O'Brien <obrien@FreeBSD.org> |
Remove multi-line __P() usage.
|
#
80578e90 |
| 22-Mar-2002 |
Warner Losh <imp@FreeBSD.org> |
const poison just like NetBSD.
|
Revision tags: release/4.5.0_cvs, release/4.4.0_cvs |
|
#
ea8d448a |
| 01-Feb-2002 |
David E. O'Brien <obrien@FreeBSD.org> |
Fix SCM ID's.
|
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 ...
|
#
bbe8edb0 |
| 02-Dec-2000 |
Garance A Drosehn <gad@FreeBSD.org> |
Fix some error-handling logic so that ferror is called before fclose, instead of immediately after the fclose. The previous logic did work on freebsd, but is somewhat risky practice (and causes trou
Fix some error-handling logic so that ferror is called before fclose, instead of immediately after the fclose. The previous logic did work on freebsd, but is somewhat risky practice (and causes trouble when porting to other OS's).
PR: bin/22965 Reviewed by: Garrett Wollman
show more ...
|
Revision tags: release/4.2.0, release/4.1.1_cvs, release/4.1.0, release/3.5.0_cvs |
|
#
8187dd1c |
| 21-May-2000 |
Tim Vanderhoek <hoek@FreeBSD.org> |
Fix a memory leak in getent() that occurred when the requested entry could not be found.
PR: bin/17084
|
Revision tags: release/4.0.0_cvs |
|
#
9233c4d9 |
| 28-Jan-2000 |
Jason Evans <jasone@FreeBSD.org> |
Simplify sytem call renaming. Instead of _foo() <-- _libc_foo <-- foo(), just use _foo() <-- foo(). In the case of a libpthread that doesn't do call conversion (such as linuxthreads and our upcomin
Simplify sytem call renaming. Instead of _foo() <-- _libc_foo <-- foo(), just use _foo() <-- foo(). In the case of a libpthread that doesn't do call conversion (such as linuxthreads and our upcoming libpthread), this is adequate. In the case of libc_r, we still need three names, which are now _thread_sys_foo() <-- _foo() <-- foo().
Convert all internal libc usage of: aio_suspend(), close(), fsync(), msync(), nanosleep(), open(), fcntl(), read(), and write() to _foo() instead of foo().
Remove all internal libc usage of: creat(), pause(), sleep(), system(), tcdrain(), wait(), and waitpid().
Make thread cancellation fully POSIX-compliant.
Suggested by: deischen
show more ...
|
#
92927338 |
| 12-Jan-2000 |
Jason Evans <jasone@FreeBSD.org> |
Add three-tier symbol naming in support of POSIX thread cancellation points. For library functions, the pattern is __sleep() <-- _libc_sleep() <-- sleep(). The arrows represent weak aliases. For s
Add three-tier symbol naming in support of POSIX thread cancellation points. For library functions, the pattern is __sleep() <-- _libc_sleep() <-- sleep(). The arrows represent weak aliases. For system calls, the pattern is _read() <-- _libc_read() <-- read().
show more ...
|
Revision tags: release/3.4.0_cvs |
|
#
49435560 |
| 04-Nov-1999 |
Andrey A. Chernov <ache@FreeBSD.org> |
Add unsigned char cast to isspace arg
|
Revision tags: release/3.3.0_cvs, release/3.2.0 |
|
#
43b4fd73 |
| 21-Mar-1999 |
Warner Losh <imp@FreeBSD.org> |
Don't be so selective about which errors cause us to continue and which ones cause us to fail. Now all open errors on the databse file will cause the next file in the list to be tried.
Submitted by
Don't be so selective about which errors cause us to continue and which ones cause us to fail. Now all open errors on the databse file will cause the next file in the list to be tried.
Submitted by: Arne Henrik Juul <arnej@math.ntnu.no> PR: 4585
show more ...
|
Revision tags: release/3.1.0, release/3.0.0, release/2.2.8 |
|
#
e8420087 |
| 16-Sep-1998 |
Warner Losh <imp@FreeBSD.org> |
Replace memory leaking instances of realloc with non-leaking reallocf. In some cases replace if (a == null) a = malloc(x); else a = realloc(a, x); with simple reallocf(a, x). Per ANSI-C, this is gua
Replace memory leaking instances of realloc with non-leaking reallocf. In some cases replace if (a == null) a = malloc(x); else a = realloc(a, x); with simple reallocf(a, x). Per ANSI-C, this is guaranteed to be the same thing.
I've been running these on my system here w/o ill effects for some time. However, the CTM-express is at part 6 of 34 for the CAM changes, so I've not been able to do a build world with the CAM in the tree with these changes. Shouldn't impact anything, but...
show more ...
|
Revision tags: release/2.2.7, release/2.2.6 |
|
#
11ea2762 |
| 26-Oct-1997 |
John Polstra <jdp@FreeBSD.org> |
Change L_SET to SEEK_SET for POSIX compliance.
Submitted by: Dean Gaudet <dgaudet@arctic.org>
|
Revision tags: release/2.2.5_cvs |
|
#
d030d2d2 |
| 18-Sep-1997 |
Poul-Henning Kamp <phk@FreeBSD.org> |
Many places in the code NULL is used in integer context, where plain 0 should be used. This happens to work because we #define NULL to 0, but is stylistically wrong and can cause problems for people
Many places in the code NULL is used in integer context, where plain 0 should be used. This happens to work because we #define NULL to 0, but is stylistically wrong and can cause problems for people trying to port bits of code to other environments.
PR: 2752 Submitted by: Arne Henrik Juul <arnej@imf.unit.no>
show more ...
|
Revision tags: release/2.2.2_cvs, release/2.2.1_cvs, release/2.2.0, release/2.1.7_cvs, release/2.1.6_cvs, release/2.1.6.1, release/2.1.5_cvs, release/2.1.0_cvs |
|
#
8b102407 |
| 22-Oct-1995 |
Poul-Henning Kamp <phk@FreeBSD.org> |
Minor cleanup, mostly unused vars and missing #includes.
|
Revision tags: release/2.0.5_cvs |
|
#
6c06b4e2 |
| 30-May-1995 |
Rodney W. Grimes <rgrimes@FreeBSD.org> |
Remove trailing whitespace.
|
#
4f512989 |
| 15-May-1995 |
Andrey A. Chernov <ache@FreeBSD.org> |
Parse ^? now, our termcap use it and some termcaps from other systems use it too
|
Revision tags: 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
|