| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
getpwent(3) or getpwuid(3) when using NIS adjunct maps. The bug was
present in the internal `nis_passwd' function. The lookup in the
adjunct map used the name passed into `nis_passwd', however no name
was of course supplied by getpwent or getpwuid. Correctly use the
name from the `struct pwd' that was found instead.
PR: bin/59962
Submitted by: Gabriel Gomez <ggomez@fing.edu.uy>
|
| |
|
| |
|
|
|
|
|
|
|
| |
in contributed sources with just a hack made possible
by bsd.sys.mk,v 1.33. This is better because it just
nulls out the warning flags rather than adding gcc(1)
specific -w option to CFLAGS.
|
|
|
|
|
|
| |
used with the contrib/ gdtoa sources as they aren't WARNS-clean.
Submitted by: ru
|
|
|
|
|
|
| |
Remove now unnecessary cast.
Reported by: alpha tinderbox
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
must first attach to the traced process. If the tracing process
exits without detaching, the traced process will be killed rather
than continued. For the duration of the tracing session, the traced
process is reparented to the tracing process (with resulting expected
behaviors). It is permissible to trace more than one other process
at a time. When using waitpid() to monitor the behavior of the traced
process, signals are intercepted: they may optionally then be
forwarded using ptrace(). Signals are generated normally by and for
the process, but also by the tracing facility (SIGTRAP).
Product of: Suffering
Sponsored by: DARPA, AFRL
|
|
|
|
| |
Reported by: sparc64 tinderbox via bde
|
|
|
|
|
|
|
|
| |
Teach sdpcontrol(8) how to talk to the local SDP server
Update man pages
s/u_int/uint
Reviewed by: imp (mentor), ru
|
|
|
|
|
|
| |
Also while i'm here s/u_int/uint
Reviewed by: imp (mentor), ru
|
|
|
|
|
|
|
|
|
|
| |
at it, use the ANSI C generic pointer type for the second argument,
thus matching the documentation.
Remove the now extraneous (and now conflicting) function declarations
in various libc sources. Remove now unnecessary casts.
Reviewed by: bde
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
incorrectly when encountering `large' groups (many members and/or many
long member names). The reporter tracked this down to the glibc NSS
module compatibility code (nss_compat.c): it would prematurely record
that a NSS module was finished iterating through its database in some
cases.
Two aspects are corrected:
1. nss_compat.c recorded that a NSS module was finished iterating
whenever the module reported something other than SUCCESS. The
correct logic is to continue iteration when the module reports
either SUCCESS or RETURN. The __nss_compat_getgrent_r and
__nss_compat_getpwent_r routines are updated to reflect this.
2. An internal helper macro __nss_compat_result is used to map glibc
NSS status codes to BSD NSS status codes (e.g. NSS_STATUS_SUCCESS ->
NS_SUCCESS). It provided the obvious mapping.
When a NSS routine is called with a too-small buffer, the
convention in the BSD NSS code is to report RETURN. (This is used
to implement reentrant APIs such as getpwnam_r(3).) However, the
convention in glibc for this case is to set errno = ERANGE and
overload TRYAGAIN. __nss_compat_result is updated to handle this
case.
PR: bin/60287
Reported by: Lachlan O'Dea <odela01@ca.com>
|
|
|
|
| |
readlocks on a rwlock while there are writers waiting.
|
|
|
|
|
|
|
|
|
|
| |
on a rwlock while there are writers waiting. We normally favor
writers but when a reader already has at least one other read lock,
we favor the reader. We don't track all the rwlocks owned by a
thread, nor all the threads that own a rwlock -- we just keep
a count of all the read locks owned by a thread.
PR: 24641
|
|
|
|
| |
Submitted by: Stefan Farfeleder <stefan@fafoe.narf.at>
|
| |
|
| |
|
|
|
|
| |
declarations.
|
|
|
|
|
|
| |
prototype from header file.
Discussed with: bde, maybe one year ago
|
| |
|
| |
|
|
|
|
| |
foo[i] = bar[++i]; /* Which operator [] will be evaluated first? */
|
| |
|
| |
|
|
|
|
| |
enable sigaltstack for scope system thread.
|
| |
|
| |
|
|
|
|
| |
Submitted by: Marc Olzheim <marcolz@stack.nl>
|
| |
|
| |
|
|
|
|
|
|
|
| |
- Remove error code that can't be returned (and original description
was not proper English)
PR: docs/57434
|
|
|
|
| |
in preparation for the merge.
|
|
|
|
|
| |
a mutex locked by another thread.
o document it: pthread_mutex_timedlock(3)
|
|
|
|
|
|
|
|
|
|
| |
waiting on a locked mutex. This involves passing a struct timespec
from the pthread mutex locking interfaces all the way down to the
function that suspends the thread until the mutex is released.
The timeout is assumed to be an absolute time (i.e. not relative to
the current time).
Also, in _thread_suspend() make the passed in timespec const.
|
| |
|
|
|
|
|
|
|
|
| |
is supported, for scope system process, kernel signal bits need to be
changed.
Reviewed by: deischen
Tested on : i386 amd64 ia64
|
|
|
|
| |
Reviewed by: silby
|
| |
|
|
|
|
| |
Reviewed by: mtm
|
|
|
|
|
|
| |
directory.
Special thanks to: valgrind
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
o Remove some code duplication between _thread_init(), which is run once
to initialize libthr and the intitial thread, and pthread_create(), which
initializes newly created threads, into a new function called from both
places: init_td_common()
o Move initialization of certain parts of libthr into a separate
function. These include:
- Active threads list and it's lock
- Dead threads list and it's lock & condition variable
- Naming and insertion of the initial thread into the
active threads list.
|
|
|
|
|
| |
PR: 44394
Submitted by: Craig Rodrigues <rodrige@attbi.com>
|
|
|
|
| |
PR: 60539
|
|
|
|
| |
Noticed by: wollman
|
|
|
|
|
|
| |
PR: 20528
Submitted by: bms (original version)
Requested by: mike (awhile ago)
|
|
|
|
|
| |
Submitted by: Lukas Ertl <l.ertl@univie.ac.at>
PR: docs/60457
|