diff options
author | gnn <gnn@FreeBSD.org> | 2012-05-12 20:38:18 +0000 |
---|---|---|
committer | gnn <gnn@FreeBSD.org> | 2012-05-12 20:38:18 +0000 |
commit | 4297c1b2d07fec7f50b70e26e3adb4d062b19e15 (patch) | |
tree | aec2772e8855e6dbaea6d8136ed0c47bcb825dee /Examples/php_flow_example.txt | |
parent | 111c75a23278cd9317f0a13867c22ee0f6c95b26 (diff) | |
download | FreeBSD-src-4297c1b2d07fec7f50b70e26e3adb4d062b19e15.zip FreeBSD-src-4297c1b2d07fec7f50b70e26e3adb4d062b19e15.tar.gz |
Add the remaining scripts from the DTraceToolkit, version 0.99, to the
vendor tree.
http://www.brendangregg.com/dtrace.html#DTraceToolkit
Diffstat (limited to 'Examples/php_flow_example.txt')
-rw-r--r-- | Examples/php_flow_example.txt | 36 |
1 files changed, 36 insertions, 0 deletions
diff --git a/Examples/php_flow_example.txt b/Examples/php_flow_example.txt new file mode 100644 index 0000000..6470daf --- /dev/null +++ b/Examples/php_flow_example.txt @@ -0,0 +1,36 @@ +The following are examples of php_flow.d. + +This is a simple script to trace the flow of PHP functions. +Here it traces the example program, Code/Php/func_abc.php + +# php_flow.d + C TIME(us) FILE -- FUNC + 0 3645535409575 func_abc.php -> func_a + 0 3645535409653 func_abc.php -> sleep + 0 3645536410511 func_abc.php <- sleep + 0 3645536410536 func_abc.php -> func_b + 0 3645536410557 func_abc.php -> sleep + 0 3645537420627 func_abc.php <- sleep + 0 3645537420652 func_abc.php -> func_c + 0 3645537420673 func_abc.php -> sleep + 0 3645538430106 func_abc.php <- sleep + 0 3645538430125 func_abc.php <- func_c + 0 3645538430134 func_abc.php <- func_b + 0 3645538430143 func_abc.php <- func_a +^C + +The fourth column is indented by 2 spaces to show when a new function begins. +This shows which function is calling which - the output above begins by +showing that func_a() began; slept, and returned from sleep; and then called +func_b(). + +The TIME(us) column shows time from boot in microseconds. + +The FILE column shows the file that was being executed. + +If the output looks strange, check the CPU "C" column - if it changes, +then the output is probably shuffled. See Notes/ALLsnoop_notes.txt for +details and suggested workarounds. + +See Notes/ALLflow_notes.txt for important notes about reading flow outputs. + |