From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 Description of problem: Using ltrace to trace a process, the process is killed during the trace with a SIGSEGV. SYS_futex(0x82123d4, 0, 1, 0, 1) = -4 +++ killed by SIGSEGV +++ Version-Release number of selected component (if applicable): ltrace-0.3.36-2.EL3 How reproducible: Always Steps to Reproduce: 1.running websphere60 2.ltrace -p <PID> Actual Results: see the following: SYS_futex(0x82123d4, 0, 1, 0, 1) = -4 +++ killed by SIGSEGV +++ Expected Results: Should keep tracing the process and not kill it. Additional info:
This can happen in multithreaded program, and the fact that it dies right after futex syscall indicates that much. This is not a bug, but missing feature: ltrace doesn't grok threads, and probably will not in its current form.