search for: wait3

...restoring the signal handler. The code below takes advantage of - * this (mis)feature by installing a signal handler for SIGCLD and - * then checking to see whether it was called. If there are any - * children to be waited for, it will be. + * We use sigsuspend in conjunction with a non-blocking wait3 in + * order to ensure that waitcmd exits promptly upon the reception + * of a signal. * - * If neither SYSV nor BSD is defined, we don't implement nonblocking - * waits at all. In this case, the user will not be informed when - * a background process until the next time she runs a real prog...

...while the function is executing are queued and the signal-catching function is continually reentered until the queue is empty. Note that the function must reinstall itself after it calls wait(), wait3(), or waitpid(). Otherwise the presence of the child that caused the original signal causes another signal immediately, resulting in infinite recursion.

Dear testers, 5.0.0-rc1 has just been tagged. Please build, test and upload binaries to the sftp. Let me know if there are any issues. I'll upload sources, docs, and your binaries to the pre-release website once they're ready. Thanks, Hans

...: TestCases/Posix/stack-use-after-return.cc (3030 of 38616) > FAIL: AddressSanitizer-i386-freebsd :: TestCases/Posix/strndup_oob_test.cc (3035 of 38616) > FAIL: AddressSanitizer-i386-freebsd :: TestCases/Posix/wait.cc (3037 of 38616) > FAIL: AddressSanitizer-i386-freebsd :: TestCases/Posix/wait3.cc (3038 of 38616) > FAIL: AddressSanitizer-i386-freebsd :: TestCases/Posix/wait4.cc (3040 of 38616) > FAIL: AddressSanitizer-i386-freebsd :: TestCases/Posix/waitid.cc (3139 of 38616) > FAIL: AddressSanitizer-i386-freebsd :: TestCases/alloca_big_alignment.cc (3140 of 38616) > FAIL: Addr...

Hi, The 6.0.1-rc2 release has been tagged. Testers may begin testing and reporting results. -Tom

Hi, I've just tagged the 6.0.1-rc1 release. Testers may begin testing and uploading binaries. Also, any tester who has not tested 5.0.2-rc1 and would like to do so please try to do this before Friday, because I would like to tag 5.0.2-final then. As a reminder to users and developers, May 18 is the deadline for submitting merge requests for 6.0.1, so there is still time to get bug fixes

...scanf.o sscanf.o ctypes.o \ - strntoumax.o strntoimax.o \ - atoi.o atol.o atoll.o \ - strtol.o strtoll.o strtoul.o strtoull.o \ - strtoimax.o strtoumax.o \ - globals.o exit.o atexit.o onexit.o \ - execl.o execle.o execv.o execvpe.o execvp.o execlp.o execlpe.o \ - fork.o vfork.o wait.o wait3.o waitpid.o system.o \ - setpgrp.o getpgrp.o daemon.o \ - printf.o vprintf.o fprintf.o vfprintf.o perror.o \ - statfs.o fstatfs.o umount.o \ - creat.o open.o openat.o open_cloexec.o \ - fopen.o fread.o fread2.o fgetc.o fgets.o \ - fwrite.o fwrite2.o fputc.o fputs.o puts.o putchar.o \ -...

Bill, For some reason the llvm-symbolizer tests fail on ppc: http://lab.llvm.org:8011/builders/clang-ppc64le-linux/builds/182/steps/ninja%20check%201/logs/stdio because it can't be started: /home/buildbots/ppc64le-clang-test/clang-ppc64le/stage1/./bin/llvm-symbolizer: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by

...estCases/Posix/shared-lib-test.cc AddressSanitizer-i386-freebsd :: TestCases/Posix/stack-use-after-return.cc AddressSanitizer-i386-freebsd :: TestCases/Posix/strndup_oob_test.cc AddressSanitizer-i386-freebsd :: TestCases/Posix/wait.cc AddressSanitizer-i386-freebsd :: TestCases/Posix/wait3.cc AddressSanitizer-i386-freebsd :: TestCases/Posix/wait4.cc AddressSanitizer-i386-freebsd :: TestCases/Posix/waitid.cc AddressSanitizer-i386-freebsd :: TestCases/alloca_big_alignment.cc AddressSanitizer-i386-freebsd :: TestCases/alloca_detect_custom_size_.cc AddressSanitizer-i3...

On Thu, Feb 8, 2018 at 10:43 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 7 Feb 2018, at 21:51, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: >> >> There's been a lot of merges since rc1, and hopefully the tests are in >> a better state now. >> >> 6.0.0-rc2 was just tagged, after r324506. >> >>

http://bugzilla.mindrot.org/show_bug.cgi?id=600 Summary: compilation of ssh-askpass or ssh-rand-helper fails on NCR MP-RAS v3.02 Product: Portable OpenSSH Version: -current Platform: ix86 OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Build system

On 31 Jul 2017, at 19:26, Hans Wennborg <hans at chromium.org> wrote: > > On Sat, Jul 29, 2017 at 4:59 AM, Dimitry Andric <dimitry at andric.com> wrote: >> On 27 Jul 2017, at 00:41, Hans Wennborg via cfe-dev <cfe-dev at lists.llvm.org> wrote: >>> >>> 5.0.0-rc1 has just been tagged. >>> >>> Please build, test and upload binaries

The Samba Team are pleased to announce Samba 1.9.18p5. It may be fetched via ftp from : ftp://samba.anu.edu.au/pub/samba/samba-1.9.18p5.tar.gz This is a bugfix release, designed to address issues that users have reported with the 1.9.18p4 release. It is intended that the next Samba release will be an alpha of Samba 1.9.19, which will contain significant new functionality for integrating Samba

...t/gen/trunk/knl/linux/usr//include -I/root/gen/trunk/knl/linux/usr//arch/powerpc/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=32 -fno-stack-protector -fwrapv -m32 -Os -W -Wall -Wno-sign-compare -Wno-unused-parameter -c -o usr/klibc/wait.o usr/klibc/wait.c ppc-linux-gcc -Wp,-MD,usr/klibc/.wait3.o.d -nostdinc -iwithprefix include -I/root/ofs/trunk/packages/klibc-2.0.2/usr/include/arch/ppc -Iusr/include/arch/ppc -I/root/ofs/trunk/packages/klibc-2.0.2/usr/include/bits32 -Iusr/include/bits32 -I/root/ofs/trunk/packages/klibc-2.0.2/usr/klibc/../include -Iusr/klibc/../include -I/root/ofs/trunk/...

On Tue, Aug 20, 2013 at 07:44:39AM +0200, leroy christophe wrote: > > > Find attached two patches I have in order to build klibc 2.0.2 > against kernel 3.8.13 > We had to introduce those patches when going from kernel 3.6 to kernel 3.7 > Hope it helps. > those patches are wrong and again very brittle. just use the way it is described in `make help': A) cd ~/src/linux

I have updated the klibc patchset based on feedback received. In particular, the patchset has been reorganized so as not to break git-bisect. Additionally, this updates the patch base to 2.6.17-git12 (d38b69689c349f35502b92e20dafb30c62d49d63) and klibc 1.4.8; the main difference on the klibc side is removal of obsolete code. This is also available as a git tree at: