PRs for tag 'dtrace'
This is an experimental report containing PRs for tag 'dtrace' as of 5-25-2012. GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '[<tagname>]' to the Synopsis field. Consider this a prototype of a better search function.
This report is generated statically.
Please give feedback on this report to linimon@FreeBSD.org. Thanks.
PRs for tag 'dtrace':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2012/04/13 | kern/166928 | gnn | [dtrace] fbt provider does not destroy probes when module unloaded |
| o | 2012/04/13 | kern/166927 | gnn | [dtrace] [modules] Kernel panics if you unload a kld module that provides probes with an active D script |
| o | 2012/04/13 | kern/166926 | gnn | [dtrace] Individual probes cannot be destroyed, only providers |
| o | 2012/04/13 | kern/166925 | gnn | [dtrace] lockstat provider only works in files that #include "opt_kdtrace.h" |
| o | 2012/04/13 | kern/166924 | gnn | [dtrace] deferred DTrace probes never match if executable linked with -E |
| o | 2012/04/13 | kern/166923 | gnn | [dtrace] kernel trap 12 with interrupts disabled (not a panic!?) |
| o | 2012/04/13 | kern/166922 | gnn | [dtrace] Wildcarded dtrace probe names not always working |
| p | 2012/04/13 | kern/166920 | gnn | [dtrace] dtrace(1) kills itself with SIGUSR1 |
| o | 2012/04/13 | kern/166919 | gnn | [dtrace] If dtrace(1) crashes while attached to a process, the process is left in a weird state |
| o | 2012/04/13 | kern/166918 | gnn | [dtrace] USDT probes not cleaned up when process exits uncleanly |
| o | 2012/02/25 | kern/165479 | rstone | [dtrace] [lor] LOR in Userland Dtrace(fasttrap_provs.fth_table[i].ftb_mtx/dtrace_provider_lock) |
| o | 2012/02/03 | kern/164724 | gnn | [dtrace] [patch] Signal bug in Dtrace |
| o | 2011/08/30 | kern/160307 | [dtrace] dtrace -lv can not identify the args of the probe function | |
| o | 2011/08/08 | kern/159612 | [dtrace] walltimestamp and timestamp functions incomplete | |
| p | 2011/07/19 | kern/159046 | rwatson | [dtrace] [patch] dtrace library is linked with a wrong flags on -CURRENT |
| o | 2011/07/18 | kern/159013 | rwatson | [dtrace] kldunload dtraceall crashing if userland dtrace provider is in use |
| p | 2011/06/29 | bin/158431 | gnn | [dtrace] crash in dt_proc_lookup when attaching to PID, assert(dpr != NULL) |
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.