| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Requested by: bde
|
|
|
|
| |
Trust me.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
don't call it according to the runtime specification and especially
WRT to gp this can cause trouble. The gcc 3.3.1 import broke the
ia64 runtime because the compiler saved gp prior to us being able
to set it properly. Restoring gp after the calls would then invalidate
gp and cause segmentation faults later on.
By rewriting _start() as an assembly function, we also avoided even
more gcc dependences, by trying to use gcc specific features to work
around the problem.
This version of _start() does not reference _DYNAMIC. We register the
cleanup function when it's a non-NULL pointer. The kernel will always
pass a NULL pointer and dynamic linkers may pass a non-NULL pointer.
The machine independent code to set __progname now unfortunately is
written in assembly. So be it.
|
|
|
|
|
|
|
| |
Update the manpage to reflect this.
PR: docs/54235
Submitted by: Karen Thode <thode12@msn.com>
|
|
|
|
| |
Submitted by: Craig Rodrigues <rodrigc@crodrigues.org>
|
| |
|
|
|
|
|
|
|
|
| |
its waitset, but if the signal is not masked by the thread, the signal
can interrupt the thread and signal action can be invoked by the thread,
sigwait should return with errno set to EINTR.
Also save and restore thread internal state(timeout and interrupted)
around signal handler invoking.
|
| |
|
|
|
|
| |
Reviewed by: deischen
|
|
|
|
|
|
| |
in the set of signals to block.
Also, make the PANIC macro call abort() instead of simply
exiting.
|
|
|
|
| |
in last commit.
|
| |
|
|
|
|
| |
Reviewed by: deischen
|
|
|
|
| |
MAINTAINER file (which already had entries for sendmail).
|
|
|
|
| |
it in one line.
|
|
|
|
|
| |
It is a more acurate description of the locks they
operate on.
|
|
|
|
| |
Roll it into the pre-existing macro that's used to call it.
|
| |
|
|
|
|
| |
in FreeBSD 6
|
| |
|
| |
|
|
|
|
|
|
| |
by sizeof(wchar_t) to get the number of wide characters it contains.
Remove the !hardway micro-optimisation from the CT_INT case to avoid
having to fix it for wide characters.
|
| |
|
| |
|
|
|
|
| |
outside of lock.
|
|
|
|
| |
Desired by: bde
|
|
|
|
| |
it only need purely wait in user space.
|
|
|
|
| |
signals.
|
|
|
|
| |
is not enough.
|
| |
|
|
|
|
|
|
| |
Record the missing dependency of thr_libc.So on the libc_pic.a library.
OK'ed by: kan
|
|
|
|
|
| |
Use THR_CONDQ_CLEAR not THR_COND_SET in cond_queue_deq, current
cond_queue_deq is not used.
|
|
|
|
|
| |
Submitted by: bde
Tested by: beast
|
| |
|
|
|
|
|
|
|
|
|
| |
is made an array of two, to explicitly avoid stack corruption due to
null-terminating (which is doesn't actually happen due to stack alignment
padding).
Submitted by: Ed Moy <emoy@apple.com>
Obtained from: Apple Computer, Inc.
|
|
|
|
|
|
|
|
| |
Create a private, single underscore, version of pthread_mutex_unlock for libc.
pthread_mutex_lock already has one. These versions are different from the
ones that applications will link against because they block all signals
from the time a call to lock the mutex is made until it is successfully
unlocked.
|
|
|
|
| |
add it to CFLAGS.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
system by specifying the file system ID instead of a path. Use this
by default in umount(8). This avoids the need to perform any vnode
operations to look up the mount point, so it makes it possible to
unmount a file system whose root vnode cannot be looked up (e.g.
due to a dead NFS server, or a file system that has become detached
from the hierarchy because an underlying file system was unmounted).
It also provides an unambiguous way to specify which file system is
to be unmunted.
Since the ability to unmount using a path name is retained only for
compatibility, that case now just uses a simple string comparison
of the supplied path against f_mntonname of each mounted file system.
Discussed on: freebsd-arch
mdoc help from: ru
|
|
|
|
|
|
|
|
|
| |
a thread receives a spurious wakeup from sigtimedwait(), so make sure
that the call to the queueing code is called only once before entering
the loop (not in the loop). This should fix some fatal errors people
are seeing with messages stating the thread is already on the mutex queue.
These errors may still be triggered from signal handlers; however, since
that part of the code is not locked down yet.
|
| |
|
|
|
|
|
|
| |
PR: docs/53488
Submitted by: Andrey Simonenko <simon@comsys.ntu-kpi.kiev.ua>
MFC after: 1 week
|
|
|
|
| |
Submitted by: bde
|
| |
|
|
|
|
|
|
|
|
| |
The old buffer was not being initialized and a later str*() op on
it would cause a crash if it wasn't initialized by a previous
call to setproctitle(3) with an actual string.
Noticed by: Ashley Penney <ashp@unloved.org>
|
|
|
|
|
|
|
|
| |
to clarify which system call accepts which arguments. Previously
the manual page gave the impression that calling unmount() with
flags of (MNT_FORCE | MNT_UPDATE | MNT_RDONLY) would downgrade a
read-write mount to read-only, which is clearly untrue; to do that,
these flags should be passed to mount() instead.
|
|
|
|
|
|
|
| |
symbols from intermediate object files, so these hacks to
get AMD64 compile are no longer needed.
Tested on: sledge.FreeBSD.org
|
| |
|
| |
|