PRs for manpage 'truss(1)'
This is an experimental report containing PRs for manpage 'truss(1)' as of Fri May 30 07:39:50 2014 UTC. See notes.
PRs for manpage 'truss(1)':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2013/05/15 | bin/178664 | truss(1) may kill process | |
| o | 2013/01/13 | bin/175269 | truss(1): truss -ff doesn't detach from processes properly | |
| o | 2012/10/26 | bin/173114 | smh | [patch] truss(1): Add Linux socket call decoding to truss (patch included) |
| a | 2010/09/03 | bin/150262 | emulation | [patch] truss(1) -f doesn't follow descendants of the linux process |
| o | 2010/02/26 | bin/144322 | truss(1) fails on 'assistant-qt4' from the port qt4-assistant-4.6.1 | |
| o | 2009/05/24 | bin/134919 | smh | [patch] add information to truss(1) when tracing linux apps |
| a | 2009/02/04 | bin/131369 | delphij | truss(1): truss -f fails to attach to child processes |
| o | 2004/09/15 | bin/71749 | [patch] truss(1): truss -f causes circular wait when traced process vforks | |
| o | 2002/10/08 | bin/43819 | [patch] changed truss(1) output for utrace calls |
Notes
GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '<name>(<section>)' to the Synopsis field. Consider this a prototype of a better search function.
Please give feedback on this report to linimon@FreeBSD.org. Thanks.
Bugs can be in one of several states:
- o - open
- A problem report has been submitted, no sanity checking performed.
- a - analyzed
- The problem is understood and a solution is being sought.
- f - feedback
- Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
- p - patched
- A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
- r - repocopy
- The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
- s - suspended
- The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
- c - closed
- A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.