On Jun 06 2017, "Dmitry V. Levin" <l...@altlinux.org> wrote:
> Why clock_nanosleep is restarted after being interrupted by a signal > handler? What kind of kernel is behaving this way? Indeed, this was a kernel bug. Thanks, Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Strace-devel mailing list Strace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/strace-devel