Bug 150262 - [patch] truss(1) -f doesn't follow descendants of the linux process
Summary: [patch] truss(1) -f doesn't follow descendants of the linux process
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 8.1-STABLE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-emulation (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-04 00:40 UTC by yuri
Modified: 2017-06-03 14:45 UTC (History)
2 users (show)

See Also:

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

Note You need to log in before you can comment on or make changes to this bug.
Description yuri 2010-09-04 00:40:02 UTC 
I tried this with skype and the resulting trace only shows the major process.
This makes it very difficult troubleshooting certain things with linux processes.
Comment 1 Alexander Best freebsd_committer freebsd_triage 2010-09-05 23:31:01 UTC 
i'm not sure truss is supposed to work with linux binaries. you might want to
consider using ktrace and linux_kdump.

the point however is: should truss work with linux binaries or not? if it's not
designed to do so it might be best to abort execution of truss of it has been
invoked with a linux binary.

opinions?

cheers.
alex

-- 
a13x
Comment 2 Mateusz Guzik 2010-09-13 17:15:52 UTC 
Does this patch fix your issue?

http://student.agh.edu.pl/~mjguzik/truss-linux-forks.patch

--
Mateusz Guzik
Comment 3 Alexander Best freebsd_committer freebsd_triage 2010-09-15 11:26:01 UTC 
State Changed
From-To: open->analyzed

Problem has been identified and a patch was submitted.
Comment 4 Alexander Best freebsd_committer freebsd_triage 2011-02-15 00:10:50 UTC 
Responsible Changed
From-To: freebsd-bugs->freebsd-emulation

Assign to people who might have an opinion about this PR.
Comment 5 John Baldwin freebsd_committer freebsd_triage 2017-06-03 14:45:14 UTC 
I can longer fetch mjg@'s patch, but fork following in truss has also been reworked to make use of ptrace()'s fork following rather than matching on system call names.  Please reopen if this is still an issue.