From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225 Description of problem: strace -fo/tmp/a -p <pid> When run against a currently running process, the process gets put into 'T' state according to ps, but strace bombs out with an error. Version-Release number of selected component (if applicable): strace-4.4.97-1 How reproducible: Always Steps to Reproduce: 1.start a program. I use httpd as an example. 2.strace -fo/tmp/a -p <pid>, where <pid> is one of the httpd child processes. 3.Get an error message, and the process is now listed as 'T' in ps, and it becomes unkillable half the time. Unkillable as in 'killall -9 httpd' doesn't kill it, a reboot is necessary. If the httpd process was serving port 80, port 80 becomes unusable until that process is gone. Actual Results: # strace -fo/tmp/a -p 1085 trace: ptrace(PTRACE_SYSCALL, ...): Operation not permitted detach: ptrace(PTRACE_DETACH, ...): Operation not permitted # Expected Results: Strace should have run. Additional info: This is happening on rh8 and rh9, and even with the latest rawhide rpm of strace: strace-4.4.97-1, I believe. Kernel 2.4.18-27.8.0.
By "I believe", I mean "I believe it to be the latest version on rawhide", not "I believe I know what version of strace I'm running."
This is a kernel issue. I have reproduced it under kernel-smp-2.4.20-9 on i686, which is the kernel this report ought to refer to if its Version field is 9.
*** This bug has been marked as a duplicate of 89057 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.