dtrace_tips

More documents

Recommendations

Info

Gotcha: Unsporting libraries●●●Regrettably, on x86 there are compileroptions that cause the compiler to notstore a frame pointerThis is regrettable because theselibraries become undebuggable: stacktraces are impossibleLibrary writers: don't do this!– gcc: Don't use -fomit-frame-pointer!– Sun compilers: avoid -xO4; it does this bydefault!
Gotcha: Unsporting functions●●●●●Some compilers put jump tables in-linein program textThis is a problem because dataintermingled in program text confusestext processing tools like DTraceDTrace always errs on the side ofcaution: if it becomes confused, it willrefuse to instrument a functionMost likely to encounter this on x86Solution to this under development...
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 and 34: Trick: Using stop and ustack●●
Page 35 and 36: Tip: Ring buffering and -c/-p●●
Page 37 and 38: Tip: Tuning the deadman●●If the
Page 39 and 40: Trick: Watchpoints via pid●●●
Page 41: Trick: Iterating over structures●
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?