| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
testing this, fix MUTEX_TYPE_COUNTING_FAST. Recursive locks now work.
|
|
|
|
| |
Submitted by: Alec Wolman <wolman@cs.washington.edu>
|
| |
|
|
|
|
|
|
| |
Made pthread_cond_wait() more similar to pthread_cond_timedwait().
PR: 8375
|
|
|
|
|
|
|
|
| |
make pthread_yield() more reliable,
threads always (I hope) preempted at least every 0.1 sec, as intended.
PR: bin/7744
Submitted by: "Richard Seaman, Jr." <dick@tar.com>
|
|
|
|
| |
Submitted by: Daniel M. Eischen <eischen@vigrid.com>
|
|
|
|
| |
collector thread running after a fork.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the thread kernel into a garbage collector thread which is started when
the fisrt thread is created (other than the initial thread). This
removes the window of opportunity where a context switch will cause a
thread that has locked the malloc spinlock, to enter the thread kernel,
find there is a dead thread and try to free memory, therefore trying
to lock the malloc spinlock against itself.
The garbage collector thread acts just like any other thread, so
instead of having a spinlock to control accesses to the dead thread
list, it uses a mutex and a condition variable so that it can happily
wait to be signalled when a thread exists.
|
|
|
|
|
|
|
| |
launching an application into space when someone tries to debug it.
The dead thread list now has it's own link pointer, so use that when
reporting the grateful dead.
|
|
|
|
|
|
| |
one renamed to SIGSUSPEND) to fix sigwait().
Submitted by: Daniel M. Eischen <eischen@vigrid.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
- Add support of a thread being listed in the dead thread list as well
as the thread list.
- Add a new thread state to make sigwait work properly. (Submitted by
Daniel M. Eischen <eischen@vigrid.com>)
- Add global variable for the garbage collector mutex and condition
variable.
- Delete a couple of prototypes that are no longer required.
- Add a prototype for the garbage collector thread.
|
|
|
|
|
|
|
| |
to fork. It is difficult to do real vfork in libc_r, since almost every
operation with file descriptsor changes _thread_fd_table and friends.
popen(3) works much better with this change.
|
| |
|
|
|
|
| |
from style(9).
|
| |
|
|
|
|
|
|
|
| |
UNIX Specification.
As with our standard mutexes, process shared locks are not supported at
this time.
|
|
|
|
| |
kernel needs.
|
| |
|
| |
|
|
|
|
|
| |
Submitted by: Daniel M. Eischen <eischen@vigrid.com>
PR: misc/7039
|
|
|
|
|
|
|
| |
are started instead of init (pid = 1). This allows an embedded
implementation quite like VxWorks, with (possibly) a single threaded
program running instead of init. The neat thing is that the same threaded
process can run in a multi-user workstation environment too.
|
| |
|
|
|
|
|
|
|
|
|
| |
initialized mutex. Statically initialized mutexes are actually
initialized at first use (pthread_mutex_lock/pthread_mutex_trylock).
To prevent concurrent initialization by multiple threads, all
static initializations are now serialized by a spinlock.
Reviewed by: jb
|
|
|
|
| |
integral.
|
|
|
|
|
| |
had to wait for the thread to exit and if the caller didn't want the
thread exit status.
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
not supposed to happen, but I have seen bogus g++ code that causes
it.
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
| |
state to running despite the SA_RESTART flag which is really just for
syscalls.
|
|
|
|
|
|
| |
I shouldn't do things early in the morning.
[...]
I shouldn't do things early in the morning.
|
| |
|
|
|
|
| |
to wrapper them) and add a couple that should have been there.
|
| |
|