| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
affects sh, ftp (and others?).
Submitted by: Max Euston <meuston@jmrodgers.com>
PR: 6516
|
|
|
|
|
| |
"da" and "od" devices. Formerly ESDI was used for them, causing
problems for fresh installations of CAM systems.
|
|
|
|
|
|
| |
PR: 7009
Obtained from: http://www.sleepycat.com/update/patch.185.html, patches 1.2,
1.3 and 1.4
|
|
|
|
|
| |
had to wait for the thread to exit and if the caller didn't want the
thread exit status.
|
|
|
|
|
| |
could I find anyone to test it, so please report any
problems to me.
|
|
|
|
| |
from libmytinfo
|
|
|
|
| |
Add #pragma weak for reset_*_mode() they will be replaced in libncurses
|
|
|
|
| |
errno during a successful malloc() call.
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
so much a "fix", rather a bandaid to buy time to fix it properly
within the thread engine.
|
| |
|
| |
|
|
|
|
| |
Don't do the libtermcap un-bump hack for anything but a.out
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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-)
|
|
|
|
|
| |
I/O for those applications that don't believe the return value of zero as
meaning that THERE ARE *NO* DESCRIPTORS READY.
|
|
|
|
| |
generation.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
getXXXXbyYYYY() interfaces yet.
Obtained from: diff relative to bind-8.1.2 sources
|
|
|
|
|
| |
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?
|
|
|
|
| |
seems to be tripping up a lot of applications.
|
|
|
|
|
| |
in the file descriptor table are exactly what the kernel knows subject
to the O_NONBLOCK flag being requested by the user.
|
|
|
|
|
|
| |
friend shmget().
PR: closes misc/6763
|
| |
|
|
|
|
|
|
| |
PR: 6903
Reviewed by: phk
Submitted by: Josh Gilliam <josh@quick.net>
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
Pointed out by: Charlie Sorsby <crs@hgo.net>
|
|
|
|
|
| |
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-)
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
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 a thread specific flag to trap the case where pthread_exit() is
called from a destructor in violation of the Posix standard.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
to destroy the RPC CLIENT handle before returning.
|
| |
|
| |
|
|
|
|
| |
to avoid recursive locking.
|
| |
|
| |
|
|
|
|
|
|
| |
Simplify the atomic lock prototype, removing the lock value.
Delete the unlock prototypes that are not required.
|
|
|
|
|
| |
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).
|
| |
|
|
|
|
| |
Pointed out by: "Steve Sims" <SimsS@IBM.Net>
|