Skip site navigation (1)Skip section navigation (2)

Site Navigation

PRs for tag 'dtrace'

This is an experimental report containing PRs for tag 'dtrace' as of 5-30-2014. 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 Thanks.

PRs for tag 'dtrace':
o2014/03/24kern/187912markj[dtrace] Getting Stack Traces of Xorg with DTrace Causes Hang
p2014/02/25kern/187027markj[dtrace] [patch] Make DTrace DOF limits configurable
p2014/02/16kern/186821markj[dtrace] [patch] dtrace_dof_init() crashes when there is no probes section
o2013/11/19kern/184085markj[dtrace] process crash when dtrace is run: dtrace -n pid<PID>:::entry
o2012/11/08bin/173484gnn[feature request] [dtrace] the current implementation requires kernel being uncompressed
p2012/09/06kern/171360markj[patch][dtrace] the fasttrap fork handler recurses on the child proc mutex
o2012/07/05kern/169657markj[dtrace] name clash between dtrace and geom.h
o2012/06/24kern/169379markj[dtrace] [patch] dtrace's timestamp variable is unreliable when the cpu goes into C3 state
o2012/06/23kern/169350markj[dtrace] Extraneous output when tracing writes with output redirect to a file
p2012/04/13kern/166925markj[dtrace] lockstat provider only works in files that #include "opt_kdtrace.h"
o2012/04/13kern/166924markj[dtrace] deferred DTrace probes never match if executable linked with -E
f2012/04/13kern/166923markj[dtrace] kernel trap 12 with interrupts disabled (not a panic!?)
p2012/04/13kern/166922markj[dtrace] Wildcarded dtrace probe names not always working
o2012/04/13kern/166919markj[dtrace] If dtrace(1) crashes while attached to a process, the process is left in a weird state
o2012/04/13kern/166918markj[dtrace] USDT probes not cleaned up when process exits uncleanly
o2012/02/25kern/165479rstone[dtrace] [lor] LOR in Userland Dtrace(fasttrap_provs.fth_table[i].ftb_mtx/dtrace_provider_lock)
p2011/07/19kern/159046rwatson[dtrace] [patch] dtrace library is linked with a wrong flags on -CURRENT
f2011/07/18kern/159013markj[dtrace] kldunload dtraceall crashing if userland dtrace provider is in use
18 problems total.

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.