dtrace_tips

More documents

Recommendations

Info

Gotcha: Slow user stacks●●●If neither -p or -c is specified, processhandles for strack symbol translationare maintained in an LRU grab cacheIf more processes are being ustack'dthan handles are cached, user stackpostprocessing can be slowedDefault size of grab cache is eightprocess handles; can be tuned viapgmax option
Tip: Ring buffering and -c/-p●●●●●Problem: program repeatedly crashes,but for unknown reasonsUse ring buffering by settingbufpolicy to ringRing buffering allows use on longrunningprocessesFor example, to capture all functionscalled up to the point of failure:<strong>dtrace</strong> -n 'pid$target:::entry'-x bufpolicy=ring -c cmd
Page 1 and 2: Advanced DTraceTips, Tricks and Got
Page 3 and 4: DTrace Tips●●●Tips are pointe
Page 5 and 6: DTrace Gotchas●●●Like any sys
Page 7 and 8: Tip: Speculative tracing●●●
Page 9 and 10: Tip: clear and tick probes●●cle
Page 11 and 12: Tip: stop●●One may wish to stop
Page 13 and 14: Gotcha: stop gone haywire●●●B
Page 17 and 18: Gotcha: Too many pid probes●●
Page 20 and 21: Gotcha: Buffer drops●●●●The
Page 25 and 26: Trick: Tracking object lifetime●
Page 27 and 28: Tip: Using system●●Use the syst
Page 29 and 30: Trick: system(“dtrace”)●●
Page 31 and 32: Gotcha: Stripped user stacks●●
Page 33: Trick: Using stop and ustack●●
Page 37 and 38: Tip: Tuning the deadman●●If the
Page 39 and 40: Trick: Watchpoints via pid●●●
Page 41 and 42: Trick: Iterating over structures●
Page 43 and 44: Gotcha: Unsporting functions●●
Page 45 and 46: Trick: sizeof and profiling●●
Page 47 and 48: Gotcha: $target evaluation●●●
Page 49 and 50: Gotcha: Data model mismatch●●
Page 51 and 52: Tip: Sample with profile●●●Wh
Page 53 and 54: Gotcha: vtimestamp●●●●vtime
Page 55 and 56: Tip: Demo DTrace scripts●●●/u

dtrace_tips

Create successful ePaper yourself

Delete template?

Save as template?