2.5.51 nanosleep fails
Quoted 5 lines · Marco d'Itri
nanosleep fails after being interrupted:
[...]
nanosleep({1, 0},
[1]+ Stopped strace tail -f/var/log/uucp/Log
Quoted 7 lines
md@wonderland:~$ fg strace tail -f /var/log/uucp/Log <unfinished ...> --- SIGCONT (Continued) --- <... nanosleep resumed> 0) = -1 ENOSYS (Function not implemented)>This can be reliably reproduced.
Hi Marco, Everyone,
I was able to reproduce this issue. It happens on all the kernels I tried including a stock Redhat kernel. This is just an idiosyncrasy of strace. In this case both the strace and tail are sent a SIGTSTP when they are put into the background. Its not suprising that this might confuse strace.
I also tried this with a program which just does a long nanosleep. Strace still shows a return of ENOSYS but the program actually gets the correct EINTR.
Jim Houston - Concurrent Computer Corp.
Quoted 3 lines · Jim Houston
I was able to reproduce this issue. It happens on all the kernels I tried including a stock Redhat kernel. This is just an idiosyncrasy of strace. In this case both the strace and
No, it is not. It does not happen with 2.4.x kernel and probably did not happen with 2.5.50.
It *does* happen with 2.5.51 even when strace is not used:
md@wonderland:~$LANG= tail -f /var/log/uucp/Log
[...]
uucico bofh - (2002-12-12 21:50:27.54 4484) Call complete (4 seconds 2336 bytes 584 bps)
[2]+ Stopped LANG= tail -f /var/log/uucp/Log
md@wonderland:~$ fg LANG= tail -f /var/log/uucp/Log tail: cannot read realtime clock: Bad address [Exit 1] md@wonderland:~$
Signature · 2 lines
ciao, Marco