DTrace patch for Python 2.7.x and 3.x

Última Actualización: 21 de septiembre de 2015

https://www.jcea.es/artic/python_dtrace.htm

You can follow this work in the Python bugtracker on issue 13405 (original work on issue 4111).

How to get the patch

You can clone my mercurial repository. Interesting branches are dtrace-issue13405_2.7dtrace-issue13405_3.4dtrace-issue13405_3.5 and dtrace-issue13405 (future 3.6). This configuration is recommended if you plan to contribute.

If you just want to compile your Python interpreter with dtrace patch applied, you only need to apply the matching patch over a pristine copy of the canonical Python source tree:

How to compile and test

Do "autoconf".

Add "--with-dtrace" to your "configure" command line and compile as usual. If you have previously compiled Python in the same directory, remember to do "make distclean" first.

When done, you should run the complete testsuite. If you just want to run dtrace tests, do

# LD_LIBRARY_PATH=`pwd` ./python Lib/test/regrtest.py -v test_dtrace.py

You should get something like

[1/1] test_dtrace
test_function_entry_return (test.test_dtrace.DTraceTestsNormal) ... ok
test_garbage_collection (test.test_dtrace.DTraceTestsNormal) ... ok
test_instance_creation_destruction (test.test_dtrace.DTraceTestsNormal) ... ok
test_line (test.test_dtrace.DTraceTestsNormal) ... ok
test_stack (test.test_dtrace.DTraceTestsNormal) ... ok
test_unicode_function_entry_return (test.test_dtrace.DTraceTestsNormal) ... ok
test_unicode_stack (test.test_dtrace.DTraceTestsNormal) ... ok
test_verify_opcodes (test.test_dtrace.DTraceTestsNormal) ... ok ----------------------------------------------------------------------
Ran 8 tests in 5.335s OK
test_function_entry_return (test.test_dtrace.DTraceTestsOptimize) ... ok
test_garbage_collection (test.test_dtrace.DTraceTestsOptimize) ... ok
test_instance_creation_destruction (test.test_dtrace.DTraceTestsOptimize) ... ok
test_line (test.test_dtrace.DTraceTestsOptimize) ... ok
test_stack (test.test_dtrace.DTraceTestsOptimize) ... ok
test_unicode_function_entry_return (test.test_dtrace.DTraceTestsOptimize) ... ok
test_unicode_stack (test.test_dtrace.DTraceTestsOptimize) ... ok
test_verify_opcodes (test.test_dtrace.DTraceTestsOptimize) ... ok ----------------------------------------------------------------------
Ran 8 tests in 5.455s OK
1 test OK.

The first set of tests run under non-optimizing Python, while the second set run under optimizing Python (-O).

Documentation

:mod:`dtrace` --- DTrace probes for Python
=============================================== .. module:: dtrace
:synopsis: DTrace probes for Python. **Source code:** :source:`Lib/dtrace.py` -------------- The :mod:`dtrace` module indicates if the CPython executable currently
running has been compiled with DTrace probes support. .. impl-detail:: DTrace probes are implementation details of the CPython interpreter!
No garantees are made about probe compatibility between versions of
CPython. DTrace scripts can stop working or work incorrectly without
warning when changing CPython versions. The :mod:`dtrace` module defines the following variable: .. data:: available The variable will be ``True`` if the current CPython interpreter was
compiled with DTrace probe support. ``False`` if not. DTrace probes
------------- DTrace scripts are run externally to CPython. DTrace probes export
selected events inside CPython interpreter in order to make them
accessible to external scripts. The probes are exported through the "python" provider. The available
probes are defined in the file :file:`Include/pydtrace.d`. To learn how to use DTrace, read `DTrace User Guide
`_. .. opcode:: function-entry (arg0, arg1, arg2) Fires when python code enters a new function. *arg0* is sourcecode
file path, *arg1* is the name of the funcion called, and *arg2* is
line number. The probe is not fired if Python code calls C functions. .. opcode:: function-return (arg0, arg1, arg2) Fires when Python code finishes execution of a function. Parameters
are the same as in ``function-entry``. The probe is not fired if the finishing function is written in C. .. opcode:: line (arg0, arg1, arg2) Fires when Python code changes the execution line. Parameters are the
same as in ``function-entry``. The probe is not fired in C functions. .. opcode:: gc-start (arg0) Fires when the Python interpreter starts a garbage collection cycle.
*arg0* is the generation to scan, like :func:`gc.collect()`. .. opcode:: gc-done (arg0) Fires when the Python interpreter finishes a garbage collection
cycle. *arg0* is the number of collected objects. .. opcode:: instance-new-start (arg0, arg1) Fires when an object instanciation starts. *arg0* is the class name,
*arg1* is the filename where the class is defined. The probe is not fired for most C code object creations. .. opcode:: instance-new-done (arg0, arg1) Fires when an object instanciation finishes. Parameters are the same
as in ``instance-new-done``. The probe is not fired for most C code object creations. .. opcode:: instance-delete-start (arg0, arg1) Fires when an object instance is going to be destroyed. Parameters
are the same as in ``instance-new-done``. The probe is not fired for most C code object destructions. .. opcode:: instance-delete-done (arg0, arg1) Fires when an object instance has been destroyed. parameters are the
same as in ``instance-new-done``. Between an ``instance-delete-start`` and corresponding
``instance-delete-done`` others probes can fire if, for instance,
deletion of an instance creates a deletion cascade. The probe is not fired for most C code object destructions. Python stack
------------ When a DTrace probe is fired, the DTrace script can examine the stack.
Since CPython is a Python interpreter coded in C, the stack will show C
functions, with no direct relation to the Python code currently being
executed. Using the special "jstack()" DTrace function, the user will be given
hints about the python program stack, if possible. In particular, the
augmented stack will show python function calls, filename, name
of the function or method, and the line number. DTrace scripts examples
----------------------- DTrace python provider is suffixed by the pid of the process to monitor.
In the examples, the pid will be 9876. Show the time spent doing garbage collection (in nanoseconds):: python9876:::gc-start
{
self->t = timestamp;
} python9876:::gc-done
/self->t/
{
printf("%d", timestamp-self->t);
self->t = 0;
} Count how many instances are created of each class:: python9876:::instance-new-start
{
@v[copyinstr(arg1), copyinstr(arg0)] = count();
} Observe time spent in object destruction, useful if datastructures are
complicated and deletion of an object can create a cascade effect:: python9876:::instance-delete-start
/self->t==0/
{
self->t = timestamp;
self->level = 0;
} python9876:::instance-delete-start
/self->t/
{
self->level += 1;
} python9876:::instance-delete-done
/(self->level) && (self->t)/
{
self->level -= 1;
} python9876:::instance-delete-done
/(self->level==0) && (self->t)/
{
@time = quantize(timestamp-self->t);
self->t = 0;
} To know which python source code lines create new TCP/IP connections:: pid9876::sock_connect:entry
{
@conn[jstack()] = count();
}

DTrace patch for Python 2.7.x and 3.x的更多相关文章

  1. 偷梁换柱:使用mock.patch辅助python单元测试

    最近在搞软工项目的后端测试,重新复习了一下python的mock.patch,并用它简化了对一些复杂逻辑的测试,在此记录 问题描述 本组的项目比较特殊,设计对教务网站的模拟登陆与信息爬取,同时不少接口 ...

  2. python 2016 大会 pyconsk ppt ---python dtrace

    https://github.com/pyconsk/2016-slides PyCon SK 2016 - March 2016 1DTrace and PythonJesús Cea Aviónj ...

  3. json-patch 了解

    What is JSON Patch? JSON Patch is a format for describing changes to a JSON document. It can be used ...

  4. Linux下编译安装源码包软件 configure ,make, make install, make test/check, make clean

    http://www.360doc7.net/wxarticlenew/541275971.html 一.什么是源码包软件? 顾名思义,源码包就是源代码的可见的软件包,基于Linux和BSD系统的软件 ...

  5. __sizeof__()

    https://bugs.python.org/issue2898 https://bugs.python.org/file10353/footprint.patch Index: Python/sy ...

  6. 应用安全 - 编程语言 | 框架 - PHP - Djiango - 漏洞 -汇总

    CVE-2007-0404 Date , 类型Filename validation issue in translation framework. Full description 影响范围 CVE ...

  7. Linux下编译安装源码包软件 configure ,make, make install, make test/check, make clean 假目标

    http://www.360doc7.net/wxarticlenew/541275971.html 一.程序的组成部分 Linux下程序大都是由以下几部分组成: 二进制文件:也就是可以运行的程序文件 ...

  8. UltraSoft - Beta - Postmortem事后分析

    UltraSoft - Beta - PostMORTEM 设想和目标 我们的软件要解决什么问题?是否定义得很清楚?是否对典型用户和典型场景有清晰的描述? 解决的问题和定义都在[软软软]功能规格说明书 ...

  9. UltraSoft Scrum Meeting 博客汇总

    一.Alpha阶段 UltraSoft - Alpha - Scrum Meeting 1 UltraSoft - Alpha - Scrum Meeting 2 UltraSoft - Alpha ...

随机推荐

  1. 转:为什么Eclipse中 按 F3 无效

    通常是由于自己的 工程 建得不对, 没有声明为 JAVA 或 PHP 类型工程. 例如, PHP 工程的 .project 文件中的内容如果如下, F3 应该就可以起作用了. <?xml ver ...

  2. GetActiveView 返回 NULL 为 MDI 框架窗口

    blog 在 MDI 应用程序中,MDI 主框架窗口(CMDIFrameWnd) 不具有与其相关联的视图.相反,每个单独的子窗口(CMDIChildWnd)具有与之关联的一个或多个视图.因此,对 MD ...

  3. Linux复制指定目录下的文件夹结构

    [root@ebs12vis ~]# su - applmgr[applmgr@ebs12vis ~]$ cd $APPL_TOP/inv[applmgr@ebs12vis inv]$ find . ...

  4. BZOJ2553: [BeiJing2011]禁忌

    2553: [BeiJing2011]禁忌 Time Limit: 20 Sec  Memory Limit: 128 MBSec  Special JudgeSubmit: 203  Solved: ...

  5. ☀【JS】eval

    避免使用 eval <!doctype html> <html lang="zh-CN"> <head> <meta charset=&q ...

  6. 关于Sublime Text2 GBK编码的问题

    很多文章都说需要"ConvertToUTF8"和"GBK Encoding Support"连个插件. 其实GBK Encoding Support完全不需要, ...

  7. ArcGIS for Android示例解析之高亮要素-----HighlightFeatures

    转自:http://blog.csdn.net/wozaifeiyang0/article/details/7323606 HighlightFeatures 要素高亮化功能,相信有其他gis开发经营 ...

  8. TinyXml和tinyxml2

    C++操作xml没有标准库的支持,TinyXml是个不错的xml操作库,以前总是使用TinyXml读写xml,但是最近对大量xml进行读写时,速度真的是有点慢,特别是在调试时,每次启动读xml就要好长 ...

  9. QT学习(对话框)codeblock版本

    参考: http://www.cnblogs.com/JohnShao/archive/2011/09/26/2191627.html http://www.cnblogs.com/xiao-chen ...

  10. POJ1226 - Substrings(KMP+二分)

    题目大意 给定n个字符串,字符串可逆序可顺序,求它们的最长公共子串 题解 在输入的过程中记录一下最短的那个字符串,然后枚举起点,然后进行二分求出子串末位置,然后再验证是否是公共子串,记录最长的公共子串 ...