Name
Date
Size
#Lines
LOC

..--

ReadmeH A D30-Sep-20151.3 KiB2921

py_calldist.dH A D30-Sep-20152.2 KiB8335

py_calltime.dH A D30-Sep-20152.6 KiB9043

py_cpudist.dH A D30-Sep-20152.2 KiB8335

py_cputime.dH A D30-Sep-20152.6 KiB9043

py_flow.dH A D30-Sep-20151.9 KiB7120

py_flowinfo.dH A D30-Sep-20152.3 KiB8733

py_flowtime.dH A D30-Sep-20152.4 KiB9034

py_funccalls.dH A D30-Sep-20151.4 KiB5615

py_malloc.dH A D30-Sep-20152.2 KiB8238

py_mallocstk.dH A D30-Sep-20151.2 KiB5017

py_profile.dH A D30-Sep-20152.4 KiB8022

py_syscalls.dH A D30-Sep-20151.7 KiB6421

py_syscolors.dH A D30-Sep-20153.2 KiB11763

py_who.dH A D30-Sep-20151.4 KiB5715

Readme

1Python - DTracing Python
2
3   These scripts trace the Python programming language, and require a version
4   of Python which has been built with DTrace probes.
5
6   The Python DTrace provider was originally written by John Levon, and
7   was integrated into Solaris Nevada in build 65. If you are on a different
8   OS with DTrace and would like to use these scripts, you could download
9   Python and the Python DTrace provider patch listed in the comments here,
10
11	http://blogs.sun.com/levon/entry/python_and_dtrace_in_build
12
13   You will need patch and build Python for these probes to work.
14   Or, check if a pre-built package is available someone on opensolaris.org.
15
16   Since the DTrace Python provider may be developed further, there is a chance
17   that it has changed slightly by the time you are reading this, causing
18   these scripts to either break or behave oddly. Firstly, check for newer
19   versions of the DTraceToolkit; if it hasn't been updated and you need
20   to use these scripts immediately, then updating them shouldn't take
21   too long. The following was the state of the provider when these scripts
22   were written - check for changes and update the scripts accordingly,
23
24	provider python {
25	    probe function-entry(file, subroutine, lineno)
26	    probe function-return(file, subroutine, lineno)
27	};
28
29