Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

For bugs related to Red Hat Enterprise Linux 3 product line. The current stable release is 3.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 168490

Summary:	ltrace kills process that you are trying to trace
Product:	Red Hat Enterprise Linux 3	Reporter:	Todd Warfield <todd.warfield>
Component:	ltrace	Assignee:	Petr Machata <pmachata>
Status:	CLOSED WONTFIX	QA Contact:	Jay Turner <jturner>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.0	CC:	mnewsome, srevivo
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-05-23 14:14:49 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Todd Warfield 2005-09-16 17:06:49 UTC

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:

Comment 1 Petr Machata 2007-05-23 14:14:49 UTC

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.