summaryrefslogtreecommitdiffstats
path: root/lib
Commit message (Collapse)AuthorAgeFilesLines
* Add CUSEEME support. This has *not* been tested, norbrian1998-06-244-2/+131
| | | | | could I find anyone to test it, so please report any problems to me.
* Fix keypad on/off for ^Z suspends by replacing reset_*_mode()ache1998-06-193-25/+53
| | | | from libmytinfo
* Add check for non-NULL cur_termache1998-06-191-0/+11
| | | | Add #pragma weak for reset_*_mode() they will be replaced in libncurses
* preserve errno across the readlink() calls. There is no value in trashingpeter1998-06-181-1/+4
| | | | errno during a successful malloc() call.
* Don't allow a SIGCHLD to wake up a thread if the process has the defaultjb1998-06-173-18/+27
| | | | | signal handler installed for SIGCHLD. The ACE MT_SOCK_Test was hanging as the result of being interrupted when it didn't expect to be.
* If a thread is waiting on a child process to complete, the SIGCHLDjb1998-06-173-3/+60
| | | | | | signal can arrive before the thread is woken from it's wait4. In this case, don't return an EINTR, just set the thread state to running and the wait4 wrapper will loop and get the exit status of the process.
* Don't compile in the use of poll() when building libc_r. This isn'tpeter1998-06-144-7/+21
| | | | | so much a "fix", rather a bandaid to buy time to fix it properly within the thread engine.
* If a short write, only loop if no error.jb1998-06-146-12/+12
|
* Document EINVAL return value.bde1998-06-141-0/+7
|
* Understand elf library naming rules for libtermlib alias.peter1998-06-121-0/+9
| | | | Don't do the libtermcap un-bump hack for anything but a.out
* Make nlist() understand elf unconditionallypeter1998-06-122-5/+2
|
* Add poll to the list of hidden syscalls so that it gets renamed. Thisjb1998-06-123-6/+6
| | | | | | | | | | | propagates a bug (that there is no poll wrapper in libc_r), but it prevents GNU configure scripts from trying to use it in preference to select. libc_r really needs to change it's wait interface to use poll instead of select because poll is more a superset of select that the other way around. This should allow the Roxen web server to work out-of-the-box. It's configuration intercae is kinda neat. The code isn't. Shiver. 8-)
* Update the caller's descriptor masks even if there are none ready forjb1998-06-123-3/+3
| | | | | I/O for those applications that don't believe the return value of zero as meaning that THERE ARE *NO* DESCRIPTORS READY.
* Sigh, mkdep doesn't know about all the CFLAGS to pass during dependpeter1998-06-111-2/+3
| | | | generation.
* Remove components that would duplicate those in libc now that thepeter1998-06-111-16/+7
| | | | | | | | includes and interfaces have been merged with the 8.1.2 update. This essentially leaves the isc/* files that named and named-xfer use. It might be best to just compile them with .PATH in both cases rather than bothering with libbind.
* Update the resolver parts to bind-8.1.2 level. I have not touched thepeter1998-06-1125-1733/+3219
| | | | | | getXXXXbyYYYY() interfaces yet. Obtained from: diff relative to bind-8.1.2 sources
* Check the access mode in the flags before waiting on a read or a writejb1998-06-1012-12/+156
| | | | | that might never be possible if the file was not opened in the corrent mode. This prevents a hang for bad programs. Why do people code like that?
* Remove SA_RESTART from the signal dispatch in user-space since thisjb1998-06-103-276/+117
| | | | seems to be tripping up a lot of applications.
* When doing a F_SETFL, read the flags back so that the ones storedjb1998-06-103-9/+93
| | | | | in the file descriptor table are exactly what the kernel knows subject to the O_NONBLOCK flag being requested by the user.
* Move ftok() from libcompat to libc, so that it can be closer to itsjdp1998-06-104-141/+4
| | | | | | friend shmget(). PR: closes misc/6763
* Fix grammar, "null" -> "NUL"danny1998-06-101-5/+5
|
* Spelling fixes.phk1998-06-101-1/+1
| | | | | | PR: 6903 Reviewed by: phk Submitted by: Josh Gilliam <josh@quick.net>
* This is a null commit to log the fact that I have done a repositoryjdp1998-06-102-2/+2
| | | | | | | copy to bring these files into libc from libcompat. I will enable them and kill off the libcompat versions on the main branch soon. PR: step one toward closing misc/6763
* Quieten gcc 2.8.1brian1998-06-101-2/+2
|
* Cast pid_t to int for sprintf.brian1998-06-101-2/+2
| | | | Pointed out by: Charlie Sorsby <crs@hgo.net>
* Add a commented out CFLAGS entry that can be uncommented to compile threadjb1998-06-093-3/+18
| | | | | lock debug into libc_r. I don't know if this is the best place to document this, but at least it is recorded somewhere. 8-)
* Implement compile time debug support instead of tracking file name andjb1998-06-0962-321/+342
| | | | | | | line number every time a file descriptor is locked. This looks like a big change but it isn't. It should reduce the size of libc_r and make it run slightly faster.
* Add compile time debug instead of doing this all the time. Reduce thejb1998-06-091-46/+333
| | | | | | | time that a thread keeps the file descriptor table locked. In particular, perform malloc/free calls outside the lock and handle the situation where two threads can race to initialise the table entry for the same file descriptor.
* Add support for compile time debug. This is enabled if libc_r is builtjb1998-06-093-60/+156
| | | | | | | | | | with -D_LOCK_DEBUG. This adds the file name and line number to each lock call and these are stored in the spinlock structure. When using debug mode, the lock function will check if the thread is trying to lock something it has already locked. This is not supposed to happen because the lock will be freed too early. Without lock debug, libc_r should be smaller and slightly faster.
* POSIX says that pthread_exit() is not allowed to be called from ajb1998-06-093-0/+30
| | | | | | | | cleanup destructor, so trap this case to prevent me from being being burnt again by applications that try to do this. With this change, an application (like one using a mis-configured ACE) will exit the process after displaying a message quoting the POSIX section that the application has violated.
* Add compile time thread lock debug support.jb1998-06-093-18/+63
| | | | | Add a thread specific flag to trap the case where pthread_exit() is called from a destructor in violation of the Posix standard.
* Remove __NETBSD_SYSCALLS from CFLAGS now that it is set in sys.mk.jb1998-06-091-2/+3
|
* Rename calls when building libc_r.jb1998-06-091-3/+3
|
* Make this thread-safe in both libc as well as libc_r.jb1998-06-091-13/+2
|
* Rename when building libc_r.jb1998-06-095-9/+9
|
* Add rename support for libc_r.jb1998-06-091-1/+50
|
* Fix potential resource leak: when call to des_crypt_1() fails, rememberwpaul1998-06-091-2/+3
| | | | to destroy the RPC CLIENT handle before returning.
* Implement compile time thread lock debug.jb1998-06-092-4/+4
|
* Rename fstat as _thread_sys_fstat if being built into libc_r.jb1998-06-091-1/+5
|
* Implement thread support for libc_r. Make the lseek syscall directlyjb1998-06-091-2/+7
| | | | to avoid recursive locking.
* Implement compile time debug mode for thread locks.jb1998-06-093-11/+11
|
* Add support for thread lock debug. No impact of the malloc code.jb1998-06-091-4/+4
|
* Implement compile time debug support for spinlocks.jb1998-06-091-5/+24
| | | | | | Simplify the atomic lock prototype, removing the lock value. Delete the unlock prototypes that are not required.
* Delete the atomic unlock function since it is no longer required.jb1998-06-093-45/+15
| | | | | Simplify the atomic lock to just write a value of 1 to the lock instead of taking the value passed by the caller (which just confused things).
* Atomic lock asm code for the alpha version of libc_r.jb1998-06-092-0/+114
|
* Don't call PunchFWHole() ifdef NO_FW_PUNCHbrian1998-06-063-0/+6
| | | | Pointed out by: "Steve Sims" <SimsS@IBM.Net>
* Fix this so that it compiles in the !__STDC__ case.steve1998-06-061-1/+5
| | | | | | Also be consistent about usage of #if ... Pointed out by: bde
* Add a warning message for a thread locking against itself. This isjb1998-06-063-9/+42
| | | | | not supposed to happen, but I have seen bogus g++ code that causes it.
* Simplify the handling of thread specific data. Only track if a keyjb1998-06-063-135/+99
| | | | | | is allocated or not, rather than keeping a count and attempting to know it it is in-use. POSIX says that once a key is deleted, using the key again results in undefined behaviour.
* Re-design the thread specific key structure.jb1998-06-063-9/+6
|
OpenPOWER on IntegriCloud