| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
...is expected to conform to IEEE (``POSIX'') Std 1003.1c when it is
published.
to:
...conforms to ISO/IEC 9945-1 ANSI/IEEE (``POSIX'') Std 1003.1 Second
Edition 1996-07-12.
Discussed with: jb
|
| |
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
pthread_mutex routines. I've also tweaked pthread_create.3 to point to
pthread_cleanup_push(3) and pthread_cleanup_pop(3).
PR: 7450
Submitted by: Brian Cully <shmit@kublai.com>
|
|
|
|
| |
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.
|
|
|
|
|
| |
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).
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
Pointed out by: Amancio
|
|
|
|
| |
on a child process.
|
|
|
|
|
| |
and modify that if the writev() syscall does not completely write
all bytes in a single call.
|
|
|
|
|
|
|
| |
written without returning to the caller. This only occurs on pipes
where either the number of bytes written is greater than the pipe
buffer or if there is insufficient space in the pipe buffer because the
reader is reading slower than the writer is writing.
|
| |
|
| |
|
|
|
|
| |
Submitted by: Tor Egge <Tor.Egge@idi.ntnu.no>
|
|
|
|
| |
PR: bin/6467 Marino Ladavac <lada@pc8811.gud.siemens.at>
|
|
|
|
|
|
| |
of the one in libc that contains the weak symbol for __error. FreeBSD's
make accumulates paths to the point that it can find *anything*, possibly
including the car keys.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for the process, not a separate set for each thread). By default, the
process now only has signal handlers installed for SIGVTALRM, SIGINFO
and SIGCHLD. The thread kernel signal handler is installed for other
signals on demand. This means that SIG_IGN and SIG_DFL processing is now
left to the kernel, not the thread kernel.
Change the signal dispatch to no longer use a signal thread, and
call the signal handler using the stack of the thread that has the
signal pending.
Change the atomic lock method to use test-and-set asm code with
a yield if blocked. This introduces separate locks for each type
of object instead of blocking signals to prevent a context
switch. It was this blocking of signals that caused the performance
degradation the people have noted.
This is a *big* change!
|
| |
|
|
|
|
| |
PS_SIGWAIT state.
|
|
|
|
| |
to EINTR.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
it was. Add a FILE_WAIT state and queue threads waiting for a FILE
lock. Start using the sys/queue.h macros instead of the way that MIT
pthreads did it.
Add a thread name to the private thread structure and a non-POSIX
function to set this. This helps (me at least) when sending a SIGINFO
to a threaded process to get a /tmp/uthread.dump to see what the
<expletive deleted> threads are doing this time. It is nice to be
able to recognise (yes, I spell that with an 's' too) which threads
are which.
|
| |
|
|
|
|
| |
POSIX specified names can be declared in pthread.h.
|