Bug 168490 – ltrace kills process that you are trying to trace

Bug 168490 - ltrace kills process that you are trying to trace

Summary:	ltrace kills process that you are trying to trace

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Red Hat Enterprise Linux 3
Classification:	Red Hat
Component:	ltrace (Show other bugs)
Sub Component:
Version:	3.0
Hardware:	i686 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Petr Machata
QA Contact:	Jay Turner
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2005-09-16 13:06 EDT by Todd Warfield
Modified:	2015-05-04 21:32 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2007-05-23 10:14:49 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Todd Warfield 2005-09-16 13:06:49 EDT

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 10:14:49 EDT

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.

Note You need to log in before you can comment on or make changes to this bug.