https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290844
--- Comment #8 from Konstantin Belousov <[email protected]> --- (In reply to Bryan Drewery from comment #7) Ok, this is much less mysterious then. I would say that the behavior that ANYSTOP/SIGCONT causes spurious EINTR is too well-established to be changed. I recently changed ptrace(PT_ATTACH) to not interrupt sleeps in this way, and it still not settled. I think that making much more common scenario change would be too much breakage. In other words, I believe that the fix belongs to sh(1) and not kernel. Perhaps sh should check if the timeout was actually reached before pretending to generate fake SIGALRM, if there is any timeout at all. -- You are receiving this mail because: You are the assignee for the bug.
