> You still need to follow the path inside > ia64_ptrace_stop() to see how any of this is possible. I tend to believe singal "deliver" in ptrace_notify path is impossible.. Given the fact that if not block SIGTRAP, the test case just works on ia64, I still believe some signals have been consumed without letting debugger know.. but it is just my guess, We still need to investigate how it happened..I assume you should know how the test case failed. PS shows the test case hangs in process 6553 which seem to be impossible ... Please help me understand what kind of situation could cause it happen. That would be very helpful. root 6516 0.0 0.0 57344 5184 ttyS1 Ss+ 19:33 0:00 -bash root 6551 0.0 0.0 4992 2560 ttyS1 T 19:33 0:00 \_ strace -f ./test1 root 6552 0.0 0.0 4416 1792 ttyS1 T 19:33 0:00 \_ ./test1 root 6553 0.0 0.0 56832 4288 ttyS1 T 19:33 0:01 \_ /bin/bash ./test2.sh Thanks, Luming -- To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|