| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
(untested, but existing state breaks
http://triangle.rtp.freebsd.org/~des/tinderbox-CURRENT-amd64-amd64.brief)
|
|
|
|
|
| |
PR: 43899
Reviewed by: des, ru
|
|
|
|
|
| |
PR: 53149
Submitted by: Lukas Ertl <l.ertl@univie.ac.at>
|
|
|
|
|
|
| |
that this file is (these files are) in the public domain.
PR: 53149
|
| |
|
|
|
|
|
| |
screwed beyond all help, so it can just skip the pthreads wrapper
for write(2) and call directly into it.
|
|
|
|
|
| |
Noticed by: ted@NLnetLabs.nl (Ted Lindgreen)
Approved by: ru
|
|
|
|
|
|
|
| |
code is always compiled into the kernel now.
Submitted by: Hubert Tournier <hubert@frbsd.org>
PR: docs/53068
|
|
|
|
|
|
|
|
|
|
|
| |
getino(3)/putino(3), inode.c has been reworked in Perforce to the point
where a manual page may not be accurate. Certainly putino(3) has not
even been merged back yet.
These will need a lot of improvement for most applications, but they
document the API enough to get someone on their feet, most likely. The
best documentation still exists in the form of libufs(3) consumers in the
base system.
|
|
|
|
|
| |
not know of any software using them, and there is no "published API" for
libufs, as it were.
|
|
|
|
| |
Parenthesise return values.
|
|
|
|
| |
MFC After: 2 days
|
|
|
|
|
|
|
|
| |
its scheduling lock, make sure that the thread still has
the signal unmasked.
Make a debug statement conditional on debugging being
enabled.
|
|
|
|
|
|
|
| |
the chance of getting the same thread id when allocating a
new thread is reduced. This won't work if the application
creates a new thread for every time a thread exits, but
we're still within the allowances of POSIX.
|
|
|
|
|
|
|
|
| |
debugging is enabled so the symbol needs to be resolved before rtld
locking is enabled. I may not really know what I'm talking about,
but it works.
Submitted by: kan
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
instead of .Xr when needed
|
| |
|
|
|
|
|
|
|
| |
looking at the host environment for anything. This breaks building
-CURRENT on 4.x as well.
Submitted by: kan@
|
|
|
|
|
| |
doesn't get fooled into returning a bogus list. This should fix sysinstall
from segfaulting when no disk devices are present.
|
|
|
|
|
|
|
|
|
| |
cat ${.ALLSRC} > ${.TARGET}
rather than
ln -sf ${.ALLSRC} ${.TARGET}
not to depends on absolute-path of symbolic links.
Commented by: marcel, obrien, bde
|
|
|
|
| |
Format other unknown devices consistently in hex.
|
|
|
|
| |
fixes lots of lint(1) warnings.
|
|
|
|
|
| |
Don't cast thread_self() to int. Cast to uintptr_t. Pull in the
predefined printf format from <inttypes.h>
|
|
|
|
|
| |
In recurse(), cast the pointer difference to int to match the format.
The difference is expected to fit in an int.
|
| |
|
|
|
|
| |
Obtained from: deischen
|
|
|
|
| |
signal mask.
|
|
|
|
|
|
|
| |
- -elf in CFLAGS had no effect except to reduce portability.
- -elf in LDFLAGS had even less effect, since LDFLAGS is not used.
- -Wall in CFLAGS had no effect except to reduce portability and break
overriding of WARNS, since the setting of WARNS implies -Wall.
|
|
|
|
|
|
| |
an application compiled -static with libthr would dump core in
malloc(3) because the stub thread initialization routine in libc would
be used instead of the libthr supplied one.
|
|
|
|
|
|
| |
don't allow it at the moment, the correct thing to do is try again.
Otherwise, libthr would fail this test because it doesn't allow
an unlimited number of concurrent threads per application.
|
|
|
|
|
|
|
|
|
| |
that the old API (passing "" as the attribute name to the _get_
interface) is now deprecated (and was probably a bad idea).
Pointed out by: Dominic Giampaolo <dbg@apple.com>
Obtained from: TrustedBSD Project
Sponsored by: DARPA, Network Associates Laboratories
|
| |
|
|
|
|
| |
Approved by: des (mentor)
|
|
|
|
|
|
| |
initialiazer.
Found by: tinderbox
|
|
|
|
|
|
| |
are destroyed.
Submitted by: tegge
|
| |
|
| |
|
|
|
|
| |
the same src/lib/libc_r/test/* tests that the other platforms pass.
|
|
|
|
| |
to a random memory location. Perl works a lot better with this.
|
|
|
|
|
|
| |
with the kind permission of the author/copyright holder.
Thanks to: phk
|
|
|
|
|
|
|
| |
hashing scheme used in Microsoft's NT machines. IT IS NOT SECURE!
DON'T USE IT! This is for the use of competent sysadmins only!
Submitted by: Michael Bretterklieber
|
|
|
|
|
| |
it's important the correct lock order is observed: lock first the joined and
then the joiner.
|
|
|
|
| |
The behaviour of this function is controlled by the argument: private.
|