GIF89a; EcchiShell v1.0
//proc/self/root/usr/share/systemtap/=N<j;E:943S20"/^.-\,H+*}(D'&%&$c#"R! nuzMlrJA q  aF eQ n                  \+Qk H0 350a ccess ndbranchescacheounters ycles exitinsnlist onperf ormance rofiling videsratiosefsscripthowing orted tp theousing:  ^ IQ81 8008Ibyevincrmmpfshowithewher,  B 8>62 65728compgomepesmto7  X0553 52950 dispatchelikprintsspentuser& 6+/47 4656+ermayprodtak# 0&*42 4166&eatmesctt$ 2"%37 3703"deviipissecu/ H!33 6120coforlopassistpvi+ @24 4629dploo processesthe& 619 4232evmoushownun& 8 14 5243 contrhofsou%  :6 5095crinpatstpvi aF2 048 aJ    , -O "c+Track Virtual Memory System Writing to Diskmmwriteback.stpmemoryThe mmwriteback.stp script uses the virtual memory tracepoints available in some kernels to report all of the file writebacks that occur form kupdate, pdflush and kjournald while the script is running. It's useful in determining where writes are coming from on a supposedly idle system that is experiencing unexpected IO.memoryk!Q1/=Collect Slab Allocation Statisticsvm.tracepoints.stpmemory statisticsThe script will probe all memory slab/slub allocations and collects information about the size of the object (bytes requested) and user-space process in execution. When run over a period of time, it helps to correlate kernel-space memory consumption owing to user-space processes.memory h4cAASystem-Wide Count of Network Packets by IPsnetfilter_summary_json.stp_best network traffic jsonThe script watches all IPv4 network traffic on the system. The data is output in JSON format and includes the number of packets sent along source IP address / destination IP address pair encountered, and the total number of bytes sent among the pair.network%3K91+print tcp retransmission packettcp_retransmission.stptcp retransmissionThe tcp_retransmission.stp prints out a line for each tcp retransmission packetnetwork[2 ?3QTrack Start and Stop of Processes Due to Network Buffer Spacesk_stream_wait_memory.stpnetwork tcp processThe sk_stream-wait_memory.stp prints a time stamp, executable, and pid each time a process blocks due to the send buffer being full. A similar entry is printed each time a process continues because there is room in the buffer.network uu*8tty aspyaurningh ypinga usedirsg  s a variousjwallntchoesnhen c ,ichjithi?riteb As b  ingmten j+xh ^)@script*a1snollingasi jecond [[!)a'+!Show Time Spent on Each Line of a Functionlinetimes.stpprofiling _bestThe linetimes.stp script takes two arguments: where to find the function and the function name. linetimes.stp will instrument each line in the function. It will print out the number of times that the function is called, a table with the average and maximum time each line takes, and control flow information when the script exits.profiling :I''TCP Connection Tracing Utilitytcp_trace.stpnetwork traceThis scripts traces a given TCP connection based on the filter parameters given by the user. The indexing is done by the 4 tuples local address, remote address, local port, remote port.networkY9w'1yDisplay Network Statistics for Individual TCP Socketstcpipstat.stpnetwork statisticsThe tcpipstat script collects and displays network statistics related to individual TCP sockets or groups of sockets. The statistics that are collected are simular to that of the command netstat -s, only sorted and grouped by individual sockets.network ((U .socket sme urce(pecified   ulationtart >9tementistics pbuch$ffixes  m`pport yscall  Astemtaptablepset  cl hat1?eu         ir nre,{irdPs  ose /read!2 #id me &ds2ingo*  : p race  d'ing ,keds * ialgger&ype writers E#7-System-Wide Futex Contentionfutexes.stpsyscall locking futexThe script watches the futex syscall on the system. On exit the futex's address, the number of contentions, and the average time for each contention on the futex are printed from lowest pid number to highest.processUs-/qTrack Creation of Processes by process and execnamespawn_seeker.stpprocess schedulerThe spawn_seeker.stp script every minute (and on exit) prints out the local time and sorted lists of which processes and executables spawned tasks during the previous minute. This can be useful to determine what process is creating a flurry of short-lived processes. When a process exits its count of tasks created is added to its parent's count to better account for the indirect task creation by children processes. For more detailed examination of task creation consider using forktracker.stp.process  !>FtoT#%)@I = p !tal qrace back points   s ) ksiggersiwo ype0 unmappingsse dful"49IrsingRvirtualmwas2"4tches point hat%en$/ "!reKther7ichle/1idell`th ,:,ork rite 5  "*ables x862you - " .yuk!aTrack a Particular Signal to a Specific Processsigmon.stpsignalsThe script watches for a particular signal sent to a specific process. When that signal is sent to the specified process, the script prints out the PID and executable of the process sending the signal, the PID and executable name of the process receiving the signal, and the signal number and name.processOtc#Track the Migration of Specific Executablesmigrate.stpschedulerThe migrate.stp script takes an argument which is the executable name of the task it should monitor. Each time a task with that executable name migrates between processors an entry is printed with the process id (pid), the executable name, the processor off loading the task, and the process taking the task. Note that the task may or may not be executing at the time of the migration.process \0pEG'yTracing of PHP code executionphp-trace.stptraceTrace of executing PHP code using the enabled markers.apps)DS+)AKeep track of NFS server statisticsnfsd-recent.stpnfs statisticsThis script tracks all nfsd server operations by client_ip address, and periodically lists those clients that have made recent requests. It's a way of finding out which nfs clients might be considered still connected.network!C;3+?Network packet contentspacket_contents.stpnetwork trafficThe packet_contents.stp script displays the length of each network packet and its contents in both hexadecimal and ASCII. Systemtap strings are MAXSTRINGLEN in length by default which may not be enough for larger packets. In order to print larger packets, this limit can be increased by passing in the "-DMAXSTRINGLEN=65536" command line option.network 11Lcreationurrent 3vesdataebuginfo  monstrate tect rmine iagnoseDfferentrectly 0skplays  tributions:oingJrawsue warf each)terdges ffective  nable )d !vents xceed-ing ecutable  s ion itspectedOtension $files  tering rst ollowed*r0#   .mat81,s unction "ality s % gameeneral7iven  ,nuplotraphingshardware ve eaderistogram7ricalow identical1f ( llustrates R ;GSummarize the time each process spends doing copy on write for huge pageshugepage_cow_delays.stpmemoryThe system may attempt to reduce memory use by having two or more difference processes share the same writeable page in memory. However, when one of the processes write to shared page that is marked copy on write (COW) the page must be duplicated and then modified. On x86_64 machines the huge pages are 2MB in size, 512 times larger than a normal 4KB page. Thus, copy on write operation on a huge page can delay program execution by a hundred or more microseconds and maybe noticeable to latency sensitive programs. This script will tally the number of times that each process triggers a huge page copy on write, the total time in microseconds spent copying the pages, and the average time in microseconds of the huge page copy.memory "@]-9SShow Process Ancestry for IP Connectionsconnect_stat.stpnetwork socket processThe connect_stat.stp script prints a task's entire ancestry (parent process name/uid/gid) whenever it attempts an outgoing socket connection to a given IP address.network?a31UTrack Creation of Incoming TCP Connectionstcp_connections.stpnetwork tcp socketThe tcp_connections.stp script prints information for each new incoming TCP connection accepted by the computer. The information includes the UID, the command accepting the connection, the PID of the command, the port the connection is on, and the IP address of the originator of the request.networkV>e/;sIncrease Initial TCP Congestion Window to 10tcp_init_cwnd.stpnetwork tcp socket guruRun the tcp_init_cwnd.stp script in the background to override a kernel's default tcp cwnd value to 10, which has been found to improve latency for web server type workloads. The script prints a count of cwnd value changes when it is stopped.network ,,Q &ofG  j    "n  ely .pen!tional |!sreut,verparameter   ser iodicallylacesyoints 1stretty vent ious'inted s+obe 1s I+cess  fileing y3example thon quantity ickread + #cv-lated iveportingspectultsturn unstime$s  aid cript: &econd6e%nd.t howing Gsimple nglexth}-zeof $$Y&65 k  a?a  - boutpccessnRumulatec dns sntivitya  iocllpongpmountnncd9b     1  yfredaf gumentjso ttempted fYributed sd udita backtracec!sedlsiisaeginn>stptweenj$lksjockf ootfthn<reakdownj usinesspyh 9tesn(6ch allc  edi$pture ghangeddsdlocknsendn0ommoncnditionesoleetainsi*unts i  umulativel decryptiongscendingl riptorhviceb s f isablehketopmummyhring c eachb   rlye syg aI!%IPrint Process File Descriptorspfiles.stpprocess fileRun pfiles.stp to produce a human-readable summary of all open file descriptors of a given process. Specify the process-id as -x PID for fastest performance.processc#GOGenerate backtraces for kernel audit eventsauditbt.stpmonitoring security backtraceAttaches to the kernel audit-log paths (also used by libaudit), and log every record being sent, along with a user-space backtrace of the process that caused it.process h^9@ completed#uterGnsiderQtains ention svert`^8@2mb94kbB512<643aY)  &CR Ux5tuser " sing variableetyousersions"wait+4  timeed7ing 3keups 2Ttcheshaten ich  leEideth0 outokenx4  #xx 4.GyProfile Kernel/User Functionspf3.stpprofilingThe pf3.stp script sets up time-based sampling. Every five seconds it prints out a sorted list with the top twenty kernel and/or user functions with samples. Use any of --ldd, --all-modules, -d MODULE, -d /PATH/TO/EXEC to add more symbolic info.profiling   C 1OLog the kernel splitting huge pages into normal sized pageshugepage_split.stpmemoryBecause some portions of the kernel code only work with normal-sized pages the kernel may convert a huge page into a set of normal-sized pages using a split operation. This operation may be relatively expensive and noticeable to latency sensitive programs. You can identify if split operations are occurring with the systemtap hugepage_split.stp script.memory+ -/ Print trace of process ancestors for matching exec commandspstrace_exec.stpprocess backtraceThe pstrace_exec.stp script watches each exec operation. If the exec contains a substring that matches the script's command-line argument, it prints out that process and all of its ancestors.process ''V/0takes tingt4skt   erminationhat!s! 'eq            is"read {)s}id{+meq0d~sy tampqo*s &  okv tal})race q pointktiggered{@unsefulsrsyvia|wait}ing} sv"tch~er sqhen uich t  levide wthq  out|x |  G7Gms]!+GGenerates a process diagram in DOT form.pstree.stpprocess diagramThe pstree.stp script generates a process diagram in DOT form. For instance, it may be useful on a 'make' command to see all the processes that are started.processzrI+} Signal Counts by Process Namesig_by_proc.stpsignalsPrint signal counts by process name in descending order.processaqY'/)Trace Time Spent in Nanosleep Syscallssleeptime.stpsyscall nanosleepThe script watches each nanosleep syscall on the system. At the end of each nanosleep syscall the script prints out a line with a timestamp in microseconds, the pid, the executable name in parentheses, the "nanosleep:" key, and the duration of the sleep in microseconds.processfp;37=monitor syscall historythread-business.stp_best process syscallPrints a periodic tabular report about the counts of syscall activity of all threads on the system, along with a textual recent-syscall-history for eachprocess#ockingg trace uckmachinekes y icrosecondsgrates4 onitoringotstutex esname  !sew nnnofileptracet;p)tlumber /observed)ccurredPf> !0  f? n"'epen ration s tionally*s 5 $r3 "der edtherut put-verflow&rides parentheses#thserformancehaps iodicallyfiles id%;  limittsrint  a )OUTrack Time Processes Spend in Various States Using Tracepointsschedtimes.stpprocess scheduler time tracepointThe schedtimes.stp script instruments the scheduler to track the amount of time that each process spends in running, sleeping, queuing, and waiting for io. On exit the script prints out the accumulated time for each state of processes observed. Optionally, this script can be used with the '-c' or '-x' options to focus on a specific PID and its children.processn 3WcMonitor process creation/termination and module [un]loadingprocmod_watcher.stpprocess monitoring syscall tracepointThe procmod_watcher.stp script monitors calls to fork(), exec(), exit(), init_module(), and delete_module(). Event-specific details are also printed out (e.g. for exec(), the file being exec'ed). This script does not require debuginfo.process //N$ ipisZs ^kernel Z least ^.(ikelier[ne [NuxZst \"onger[major^3ny\- xmapentries\;y\5easures ^ icroseconds[nor^4ost ^sYname]umber[9 5:o] f&Z  3   nY$Jly(Q        pen[ s[0ration[ s\19/tion\Ial`r [der]ut]put ^standing\.per Yiodic`ally]rint]sZ(!ocess]esZorZ filesYing ^queue\ read^ % ing^s ^:1ceivedY ordYference(Qgexp`mote[quests\scfZript&Y!econds \%tors` N G'#Callgraph Tracing of Tcl codetcl-trace.stpcallgraphPrint a timed per-thread microsecond-timed callgraph of executing Tcl code.general>/'9Callgraph Tracingcallgraph.stpsimple trace callgraphPrint a timed per-thread microsecond-timed nested callgraph. The first parameter names the function probe points to trace.general2/)Profile Tcl callstcl-funtop.stpprofilingThe tcl-funtop.stp script displays a top-like view of most frequently used Tcl functions for the each five second interval.general9c%-SWatch a Variable Changing Value in a Threadvarwatch.stp_best monitoringThis script places a set of probes (specified by $1), each of which monitors the state of some context $variable expression (specified by $2). Whenever the value changes, with respect to the active thread, the event is traced.general $X$1S%1OWatchdog Timer for Arbitrary Eventswatchdog.stpwatchdog backtraceThe watchdog.stp script provides a watchdog timer mechanism for arbitrary events. The script takes three arguments: the events to start watchdog timer, the event to stop the watchdog timer, and the time in millseconds for the watchdog. If the watchdog timer is exceed, the script will trigger a stack backtrace of the user-process that timed out using pstack. This script can be used to diagnose what the userspace application is doing when a slower than expected operation occurs.general%=33=Function Time Statisticsfunc_time_stats.stpfunction statisticsThe func_time_stats.stp script tracks the wall clock time for each invocation of the function probe listed as the first command line argument. When the script exits it prints out the minimum, average, and maximum times in microseconds followed by a count of times that the function was called and a histogram showing the distributions of times.general HM/Tracing glib2 memory allocationsgmalloc_watch.stptraceThe gmalloc_watch.stp script from Colin Walters' blog (https://blog.verbum.org/2011/03/19/analyzing-memory-use-with-systemtap/) traces the allocation of glib2 memory using the markers in glib2.appslG=1/WTrace libguestfs startuplibguestfs_log.stpapplication traceThe libguestfs_log.stp script prints a log of when various libgueststartup steps are encountered. The first column is microseconds since the script started. The second column is the time elapsed in microseconds between the previous and current events and the third column is the event name.appssure quantity between different probe points, aggregate the measurements, and display the results. The first argument to the script is the quantity to measure such as time in microseconds via "gettimeofday_us()". There could be multiple intervals being measured concurrently and the second argument is the means to match the start probe points listed in the fourth argument with the end probes listed in the fifth argument. The third argument is how to display the aggregated data. The data could be displayed as a sum (@sum), an average (@avg), or a histogram (@hist_log). The fourth and fifth arguments are lists of probes marking the start and end of an interval. An optional sixth argument allows grouping of the intervals. One could use "tid()" for the matching argument to measure the intervals on a per-thread basis, but then use "execname()" for the optional argument to group the measurements by executable name. If there is no sixth argument, all the intervals are aggregated into a single entry.general 9w g%!WKeep a tally of executables run on the systemalso_ran.stpprometheusThe also_ran.stp script tallies each time a executable is started or a shared library is loaded for execution. This information can be useful to determine what software is actually being used on the system. The script makes the information available via procfs in Prometheus readable format.generalD M17iCallgraph Tracing with Argumentspara-callgraph.stp_best trace callgraphPrint a timed per-thread microsecond-timed callgraph, complete with function parameters and return values. The first parameter names the function probe points to trace. The optional second parameter names the probe points for trigger functions, which acts to enable tracing for only those functions that occur while the current thread is nested within the trigger.general &$%/O!+ETrace Activity on Network Devicesnetdev.stpnetwork trafficThe netdev.stp script traces configuration and transmit/receive activity on network devices.network .=##+Watch autofs4 Operationsautofs4.stpnetwork nfsTrace key autofs4 operations such as mounting or unmounting remote filesystems.network-M++qDump of Received UDP/TCP Packetstcpdumplike.stpnetwork trafficThe tcpdumplike.stp prints out a line for each TCP & UDP packet received. Each line includes the source and destination IP addresses, the source and destination ports, and flags.networkW,q'?mWatch Where Socket Buffers Are Freed in the Kerneldropwatch.stpnetwork tracepoint socketEvery five seconds the dropwatch.stp script lists the number of socket buffers freed at locations in the kernel.network YA5!'uprobes-based ltraceltrace.stpprocessThe ltrace.stp script lists calls that the designated process makes through PLTs (procedure linkage tables), generally into shared libraries.processQ'+'Trace Time Spent in wait4 Syscallswait4time.stpsyscall processThe script watches each wait4 syscall on the system. At the end of each wait4 syscall the script prints out a line with a timestamp in microseconds, the pid, the executable name in parentheses, the "wait4:" key, the duration of the wait and the PID that the wait4 was waiting for. If the waited for PID is not specified , it is "-1".processU3}System-Wide Count of Syscalls by PIDsyscalls_by_pid.stpsyscallThe script watches all syscall on the system. On exit the script prints a list showing the number of systemcalls executed by each PID ordered from greatest to least number of syscalls.process ff=2small ome   rted  (pacewn edendstulit  tingtack  prting tistics <plQ:41ubstringmmarizeymbol scall tem tap7 .t7akellyaskE s erminated $&han?t( ,."Fe)   )            /  -n/is3!1D6^usDime0@ r s=*tamplb eIS5= )Time Statistics on KVM Exit Reasonskvm_service_time.stp_best virtualization kvmThe kvm_service_time.stp script tracks the statistics about the amount of time that the processor left the guest virtual machine for each exit reason (for example fixing up a page table or handling an IO operation). When the script exits it prints out the number of times each exit reason was encountered, the total duration of time it left the guest VM, the minimum time, the average time, and the maximum time in microseconds for that exit reason. On Linux 2.6.38 and newer kernel the script can automatically determine whether it is running on Intel or AMD processors. For older kernels with a kernel.trace("kvm_exit") tracepoint that does not have the $isa parameter you can explicitly state the kvm type with a "-G kvm=intel" or "-G kvm=amd" on the command line.virtualization  ]M3!Measure intervals between eventsmeasureinterval.stpmonitoringThe measureinteval.stp script allows quick creation of instrumentation to mea*@M+Color Table for ansi_set_color()ansi_colors.stpformatThe script prints a table showing the available color combinations for the ansi_set_color() function in the ansi.stp tapset.general]]A+Callgraph Tracing with Verbose Argumentspara-callgraph-verbose.stptrace callgraphPrint a timed per-thread microsecond-timed callgraph, complete with pretty-printed function parameters and return values. The first parameter names the function probe points to trace. The optional second parameter names the probe points for trigger functions, which acts to enable tracing for only those functions that occur while the current thread is nested within the trigger.general ))T,1 $( a2! 0 ccept%2close%tivity/ ddress0 es-ka+ll " so()ndG!     re) gument(s$ t,utofs4 .verages$$basic!e$ing )st!yond$" iolatency$tesize#lock #uffers,t "y $&   call"n $tch(!haracteristics$lient0ose% ommand'on " nfiguration/nections%sumed(unt&s&pu # debuginfo"        stination-tails"  vices/isk $  tribution# s$4o "  ropwatch,ump-ration%s+ ynamically "each"   11hI+UPrint Process File Descriptorspsig.stpprocess signalsRun psig.stp to produce a human-readable summary of the signal handling configuration of a given process. Specify the process-id as -x PID for fastest performance.process ~[++{Watch semop(2)/semtimedop(2) operationssemop-watch.stpprocess lockingPrints a timed trace of semop(2)/semtimedop(2) syscallsprocessT}}59SGenerate Backtraces of Threads Waiting for IO OperationssleepingBeauties.stpio scheduler backtraceThe script monitors the time that threads spend in waiting for IO operations (in "D" state) in the wait_for_completion function. If a thread spends over 10ms, its name and backtrace is printed, and later so is the total delay.process %@e'sTrack Virtual Memory System Page Reclamationmmreclaim.stpmemoryThe mmreclaim.stp script uses the virtual memory tracepoints available in some kernels to track page reclaim activity that occurred while the script was running. It's useful in debugging performance problems that occur due to page reclamation.memoryWa+#Summarize Process Misses across NUMA Nodesnuma_faults.stpmemory numaThe numa_faults.stp script tracks the read and write pages faults for each process. When the script exits it prints out the total read and write pages faults for each process. The script also provide a break down of page faults per node for each process. This script is useful for determining whether the program has good locality (page faults limited to a single node) on a NUMA computer.memory ))T', eatmydatahnospce triesmveryk   xecutableb,I sl itscfasterhewfilebs k  ystemerst f Nore  ,&romcsynchuncitionsi getmnutlsgreatestiuru a histogramcrypooksa ild b  entifiedhmplementationsenc % + dicationse ode bwatchb 2dternale oho|a statjtimenhsi/tnkerneliystrokesawordnSleast c'inenOsn8st c jsnTogkgeremachinejjor bster gbrwatchf XX%:Ngood;rouphardware $(s:ving ighest&oweveruge 6" page8 /ndredSw identify / $f 0 % mplementation roven"  0 @&; directDsternalo    vocationss,'3#%"#tG%s 3 !kernel"   smalloc larger>tency * [eaks <Limited?s  nest)sved-ocality<kingg >west"m>achines4jor 0lloc  nypped?ingrked$tchesingy beX gg0pattern er ingpongpedoints  wer rint s  obe  cess -8For * s  fs 4- gressivelymetheus 6/vided"sstack= y2example thon ran eadable 70cord s8duce  flecting gex peatedlyBort turn un time'script2# "$econd s"e 7t hared owing%8imple ulatedzeof5lidingowerMoftware urce9pace/eed  nds tack3pgames(rted  tesistics sopwatch es   q});Track Virtual Memory System Actions on File Backed Pagesmmfilepage.stpmemoryThe mmfilepage.stp script uses the virtual memory tracepoints available in some kernels to track the number of faults, copy on writes mapping, and unmapping operations for file backed pages. When the script is terminated the counts are printed for each process that allocated pages while the script was running. The mmfilepage.stp script is useful in debugging leaks in the mapped file regions of a process.memory $$Y+610ms}2~0x,5v 5 vaGq!  bout vll sson td3q'1   8 pplied|res gumentt st q Averagew backtrace {:! s}es?ingst vtweentyr c| allx s x ny hanges{ng{ ombinationymandspletion} nfigurationv'tainsv&entionw swuntzs r pu{reationd}ebuginfo'faultxlay}*etescendingr riptorstailsiagram s fferent{"oes$ts urationq)eachq d!mulates|ndq tire|ryt \\(wS%77System-Wide Shared Futex Contentionfutexes2.stpsyscall locking futexThe script watches just shared futex syscalls on the system. On exit the futex's key, the number of contentions, and the average time for each contention on the futex are printed from lowest pid number to highest.processvvs#;1Periodically Print Process Information With Historyproctop.stpprocess scheduler _bestEvery 5 seconds, print out a list of 25 processes that took the most system time with information about the processes. Includes information on processes that may have exited while the script was running. The script contains configuration options listed in the script source.process $$aFmounting.ulti$2name#  d2"_Bevery (+xample$*ec(s(3noop(ution(its!file"w !!\L< increasedadication.fo3/:rmation- 6itiallystrumenttervalo5ctl  s9 !&>  (suesCt'#" ! s/.,kernel'  1sjournald retprobes\updatelarger'st tency @ rTSPdd&"-eadIHFkingst 0ibc  mitations=<:neitimes ux st  . s ogngerwerXWTmachineslkhkes! nipulateximum .y ])be=BA?emory)$ ssage( icroseconds;  ]>lookups5 mac7y1emory2name1 s=et8filter1 stat9top6work1 w? fs5 d =top5ot1 umber4of92   (n4   'ly 1( !peration= s=tion<#s<r 1 /dered;/iginator?.ut3 going 1put4verride> packet3 s1!ir 4!  s;<rameters: ent@ ticular<eriodic6ally<id2 ort1  #ssible=rint3ed2ing1s-2 %obes1 cess2" ed6 &&W<2per,formance  lfaults id #%ortionsreviousint 0ed (*s$ & oblems!cessM& +(-hes gram9O s , ]vide%strace ranAead  3claimmation'ducefuses gions APlatively%portsqueststrictedoot !un ning35ss=Hamechedulerript_;! _2eeker nsitive + \rvicing!thared ort,w ignificantmplengleB  ze;d      ccumulates !tive@s 'ually ? lso mount#n #d7     % "imationsi y pplicationHrbitrary chive *e!guments ounds  t  &tribuestes vailable 2+erage$oid  backtrace4 s llsed e (AAcause6ing !st  lock s old uncesreakery +called4graph  n @@eiling lassicearing ock olor s2 mbinationsmand5parable1ilationlete   nstraints  rrespondingunt-pu   0 76219041a  )ction5nd) pplicationsrebasedecause3log com developersoingentry findorhelptmltp is livejournal mentioningonitors$needoccurred6nce< perationsut/polling rocessesCfiling rather0ecords*turned2screen;ipt econd>howome4tp   ystemcall% s,than1te  imed.out  oolpAwentyBudrepper pdates9sed&with? A!virtual IizationImIAwaitMQedM>ingLMsM ltersH s I6|tchHyDellLhenF- (Tther I_ ichC  ideAllLc#thA'lkrittenJ0youIy $$a2Flikemits  ne kagest  s Aved$`1D dispatched maxmapentriesue'ration(each  f YNYq$?1=MLog recent free(3) calls.last_100_frees.stpmemory process backtraceThis script reports on the last few free(3) libc calls done by processes (possibly restricted by stap -x/-c), along with a userspace backtrace at those moments.memory.# ?Summarize the time each process spends clearing huge pageshugepage_clear_delays.stpmemoryWhen a huge page is initially used by a process it must be cleared of its original contents to avoid leaking information between processes. On x86_64 machines the huge pages are 2MB in size, 512 times larger than a normal 4KB page. Thus, clearing a huge page can delay program execution by a hundred or more microseconds and maybe noticeable to latency sensitive programs. This script will tally the number of times that each process triggers a huge page clear, the total time in microseconds spent clearing the pages, and the average time in microseconds of the huge page clear.memory5@    ccess2 $ed s ountArosstionsveFitydded9ress*  ffectllocated -/ionw #so$mountncestors"dJ '  2 .+$onymous  re$3'O)8*guments  ttempt vailable   erage  {backed tracee$!$G-,cause tter@reak'point #'yG  Icalln .F,M#ertainAhildrenHodellapse ( ingect mmands HE+ 'aSummarize read() and write() syscall latency (non-debuginfo)rwtime-nd.stpioThis traces read() and write() syscalls, producing a histogram summary of their durations (aka latencies).lwtools* A-';Measure the distribution of file system synchronous read and write latency (non-debuginfo)fslatency-nd.stpio filesystemThis dynamically traces two common file system functions: do_sync_read() and do_sync_write(), and reports a histogram distribution of latency. Many, but not all, file systems and workloads use these functions. Tracing their time provides one view of suffered file system latency.lwtools5){-GTrace open() syscalls showing filenames (non-debuginfo)opensnoop-nd.stpioThis traces the open() syscall system-wide, to show which files are being opened, and by who.lwtools  )'CLog Failed Process Memory Allocation Due to Overcommit Limitsovercommit.stpmemory limitsThe overcommit.stp script prints a line each time the kernel refuses a memory allocation request from a process because of /proc/sys/vm/overcommit* limits.memoryBy)aTrack Virtual Memory System Actions on Anonymous Pagesmmanonpage.stpmemoryThe mmanonpage.stp script uses the virtual memory tracepoints available in some kernels to track the number of faults, user space frees, page ins, copy on writes and unmaps for anonymous pages. When the script is terminated the counts are printed for each process that allocated pages while the script was running. This script displays the anonymous page statistics for each process that ran while the script is active. It's useful in debugging leaks in the anonymous regions of a process.memory HH:_q#%[List Executables Reading and Writing the Most Dataiostats.stpio profiling The iostat.stp script measures the amount of data successfully read and written by all the executables on the system. The output is sorted from most greatest sum of bytes read and written by an executable to the least. The output contains the count of operations (opens, reads, and writes), the totals and averages for the number of bytes read and written.iox^ )%;List Executables Reading and Writing the Most Data by Deviceiodevstats.stpio profiling The iodevstats.stp script measures the amount of data successfully read and written by all the executables for each io device on the system. The output is sorted from greatest sum of bytes read and written to a device by an executable to the least. The output contains device major/minor number, the count of operations (reads and writes), the totals and averages for the number of bytes read and written.io TT,1 +EqTrace threads sending network traffic to given host and/or portwho_sent_it.stpnetwork trace traffic simpleThis script traces outgoing network packets using the netfilter probes (not requiring debuginfo), printing the source thread name/id and destination host:port. It may be filtered with the_dport and the_daddr globals, e.g., to watch only for DNS traffic (port 53), and/or only to the localhost (127.0.0.1).networkz0o+SFind Which Client Is Removing NFS Files on Servernfsd_unlink.stpnfs diskThe nfsd_unlink.stp script lists the ip address and file name each time time a file is being removed or unlinked by the nfsd. This script is run on the nfs server.network P1P]'[!1Show Processes Doing Polling Operationstopsys.stpprofiling The topsys.stp script lists out the top twenty systemcalls for the previous 5 seconds. The output is sorted from most frequent to least frequent.profilingS&[#+Show Functions Taking Longer Than Usualfntimes.stp_best profilingThe fntimes.stp script monitors the execution time history of a given function family (assumed non-recursive). Each time (beyond a warmup interval) is then compared to the historical maximum. If it exceeds a certain threshold (250%), a message is printed.profilingt%M71ECount Times Functions Are Calledfunctioncallcount.stpprofiling functionThe functioncallcount.stp script takes one argument, a list of functions to probe. The script will run and count the number of times that each of the functions on the list is called. On exit the script will print a sorted list from most frequently to least frequently called function.profiling $$Y,6errorsxsnoopxventryvxec utableq     stedzingt@itw   edvfailingxurexstestew|ileteredyingyrstxor s  k ms und{rom w"unction}s{>tex w es2wg |!enerate}ssivensx!reatestzhandlingveveightx$ ierarchies| ghestw'storyvumanidt&*syf}n(q  * cludesvdividual|  formationvit stancestervalxo } st  "tss}justwkernel{=y q&later}%eastzineqsx'st vedv)oadingt. cking wosely|westw#makes a2[#7Show Processes Doing Polling Operationstimeout.stpprofilingThe timeout.stp script is based on a blog entry (http://udrepper.livejournal.com/19041.html) mentioning a need for a tool to help developers find applications that are polling. The timeout.stp script monitors systemcall used for polling and records the systemcalls that timed out rather than returned because some action occurred. The script updates the screen once a second with the top twenty processes.profiling  ].>producesigtreesreadable ceivingu-portx&ingxquire&unning v#swchedulertreenx#iptCq!  !econdxs vesmop ~timedop~ ndingu"tu t|haredwellyould twing z;igrmonunalr    sr leepq, ingbeauties}timeqo}&urcev-pecifict edusxynd} s}tqtartedste {7isticsypZqrace|ummary yscall.q sq! timesytem(q    callsztapytabularxtexpy %"*ingvunt4 s&('w (reated7ing(onF debugging;KlayNstailedLermine $Jing6 ifferencesplays8oingwn(ue $plicated-ringeDach>* ,  glapsed?very xaminationMedHclude@ec  name utablesionPit   s2$pensive&failedult  s  Nile%tered.rst3lurry*or2B   9 ktrackerSreesom !unctiontex  esgenerateslibc  %%X4stpe6ream uffupport ystem %tap tablekesllies y pset erminaltedHhanNt*(# /093eq     $   ! m &rmal is)>ose -read 0eottle d ,ing ughilesme&%  "d :r   s' o*,#*#race ing *ks ialgger $1ype  s" underline til  Dse d "Bful r /7space Gs ing  < tilization values  riable  ous !!\#<deviceY   seeks`ifferent`sk` maxmapentries\Guring]eachY  ducation(Q        mergency(Qvery[#xceed\6ecutable ^+% s] itZ%pensiveZ  filesystems[ve]orDQ 08requency Z- om ^unctionZ generates`ing] iven`reatest ^uru(Qhighly[stogram` s`rical(Qt[i] dentifyZnZ+&creased\EterZ  processorZruptY sY val]o7[blktime\devstats^stat_s_top]piZ# = +N=co'%Tally Reschedule Reason During AIO io_submit Callio_submit.stpio backtraceWhen a reschedule occurs during an AIO io_submit call, accumulate the traceback in a histogram. When the script exits prints out a sorted list from most common to least common backtrace.ioZbW)CMonitoring Reads and Writes to a Fileinodewatch.stpio The inodewatch.stp outputs the executable name and process id each time a read or write occurs to the specified inode on the specified major/minor device.io]a1!9OMonitor TTY Typingttyspy.stpio tty monitoring guruThe ttyspy.stp script uses tty_audit hooks to monitor recent typing activity on the system, printing a scrolling record of recent keystrokes, on a per-tty basis.ior`c+aHistograms of Seek Behavior for Each Devicedeviceseeks.stpdiskThe deviceseeks.stp script generates a periodic histogram showing the frequency of different sized seeks (in sectors) on each device, or optional given device-name regexpio yb0 747againMll4nd$%re0gument s (sbased e /ing2can /urrentCdisplays3first unctiongetsJ happening)if-nLdicatest2nameo.on!rutApassedidrint%ocessfiling sched ule@dKr 'riptecondtp witch es(takessks?he  is8o-racedFwo understand=sed;whatenHich>illth*nd try ventsryxecutable  edit  fastestileslurry ocus 7 &r* 4  ktracker rom  utex generallyteiven  libc reatesturu handler eavy) ierarchiesstogram s7umanid entifiedy f 5#n!  itialization struments  terrupt s>ovokeorq s :Ht =s=kernelsy&large!tency  ddeastngth:ibaudit c%raries rror ONs &&W2dport1ue2mp 7ring6#e1$ach2    ncountered 4"!tire@ ry2very6 xecutable2 it; file=ter: ed1ing<ve6lags7ocus<r1)  mat 4und>rom;0ull2g1%athers5id@ven1  lobals1#reatest;1ouped9$s9uru>h<"as>ighest<ost1 id 1f=mprove>n2) cludes 4 oming? rease>dexing:ividual9  formation 8 it>ial>terfaces6val6%p4 *s4  v4 4s$2  ..&t1 -json4keep5rnel>latency>east;3ine 3 st6  ing6s<$ocal:host13 *B*7#ITrack SIGKILL Signalssigkill.stpsignalsThe script traces any SIGKILL signals. When that SIGKILL signal is sent to a process, the script prints out the signal name, the destination executable and process ID, the executable name and user ID that sents the signal.processuE)y Signal Counts by Process IDsig_by_pid.stpsignalsPrint signal counts by process ID in descending order.processC+/#Trace Creation of Processesforktracker.stpprocess schedulerThe forktracker.stp script prints out a time-stamped entry showing each fork and exec operation on the machine. This can be useful to determine what process is creating a flurry of short-lived processes.process)Y/Otrack wakeup-to-dispatch latency statssched-latency.stpprocess scheduler time tracepointThis script periodically reports a histogram of the latency between a task (thread) being woken up and it actually being dispatched to a CPU: the amount of time it's spent in the runnable queue.process ++R(for3C#I49&# rom B#unctionB4 sBgIenerateFuionFZlib2HmallocHuest I-ruA handlingI$sF4]veDu eldL}pL xadecimalC istoricalNolderLqing L6ettpsH ifAh~n)B  )! LdcomingAreasedC0dicateMs A/3 formationM_putJ strumentationF'D sBtegerA*lId"oF)oI&  pD s-A  aaIwsuesFktD,%"sCkeepDrnelB 7Y GsIjvmInlargerC$stB;eftI-ngthC  ibguestfs GstartupG mitC-neB$8Mux B SstKs D &$ ub&u.Y[7=Record Interrupts on a Per-Device Basisinterrupts-by-dev.stpinterruptThe interrupts-by-dev.stp script profiles interrupts received by each device per 100 ms.interruptXK/'1cve-2015-0235 security band-aidcve-2015-0235.stpsecurity guruhistorical emergency security band-aid, for reference/education onlysecurity-band-aidsWK/'1cve-2017-6074 security band-aidcve-2017-6074.stpsecurity guruhistorical emergency security band-aid, for reference/education onlysecurity-band-aidsVK/'1cve-2015-3456 security band-aidcve-2015-3456.stpsecurity guruhistorical emergency security band-aid, for reference/education onlysecurity-band-aids UU( Thackeaderisthogram gFowS ifn'  )cludes  formation  + strumentation  teractiveval zs 0UovocationkedCos!7V& t *kernel yboard   codeshackstrokeslanguageeroyvelifeke stedA spogimakesrkingstch<ingximum1eans:sure ld2interval valmentsmory icrosecond s (4ghtnimum.odeified"ulenitoringsre*st ultiple/name s ested 8 oisesumerousoccur2 cc_B0151170>27144:531-a-2  ,\unlink0ed0mounting. se "% ful$s#various'iew "-(was# tch,hen#re,ich ( o)ide&ll( th&orkloads "$s(ld! rite" s" {Npc8i/; Tracks time between packet queue and transmit.net_xmit_json.stpnetwork statistics jsonThis script tracks time between packet queue and transmit. The information is provided to userspace via procfs in JSON format.network[73%+IDump of STP packetsstp_dump.stpnetwork trafficThe stp_dump.stp prints out the packet contents. Each block contains the STP protocol ID, version ID, flags, root and bridge MAC addresses, and various times.network*6y!+%Periodic Listing of Processes Using Network Interfacesnettop.stpnetwork trafficEvery five seconds the nettop.stp script prints out a list of processed (PID and command) with the number of packets sent/received and the amount of data sent/received by the process during that interval.network5S#)}Keep track of NFS server statisticsnfsdtop.stpnfs statisticsThe nfsdtop.stp script gathers and displays NFS lookups,network ==_Bthez1             re2&is1read1s1ime 2 s7o/1&   2 tal 4%$race1 s1 ing:k 2 s8ffic#1+nsmit8 uples:ype>!s<uid ?ser:space8ing1tility:value>rious7ersion7ia8wait2tch1'es 4eb>hen>,ever@ich>o1ide4ndow>th1 orkloads>"xmit8 G6=)Profile Kernel Functionspf2.stpprofilingThe pf2.stp script sets up time-based sampling. Every five seconds it prints out a sorted list with the top ten kernel functions with samples.profilingC5s%aShow the Period of the Various Timers on the Systemperiodic.stpprofilingThe periodic.stp script uses the kernel.trace("timer_expire_entry") tracepoint to collect data on period and frequency of the various timers on the system. The script displays a sorted list of the timers observed on the system from most frequent to least frequent. The script needs to be compiled with the '--all-modules' option to produce list the function names. Optionally, this script can be used with a numerical argument to indicate the interval in seconds between printing output.profiling names)s) ystem " s. nd0ve,lags-or $)  k(reed,om %slatency*slower"unctions "  general!hello! world!istogram$ i#d&entify $e$ f(, mmediately! plemented!n ! cludes # ing '-sert# ed#%o-"stat$'p - s" sue#(t !  kernel # y.ill' snoop' latencies+y"2 ifespan%ne ( sts , ved( ocations,wtools2"many "eans(sure #s$ssage!odal$3 $$YK6every   xceeding:97s"ssive ec.*5utable $ T' sion5it$Es.:-+ periencing3failed9milyewile line s nd ve   low5ntimes or$  ] M*R' Ybidden#mat*)'ree squently.om$+,431unction3   q callcount s gFathered!ive+n ood-reatlyuruDhandlecdr ;ing 5vejelpAs$ istoricaly uge  "pagendred8idle/f QYn2 #5 &N$@clude<d /o/W9Provide a per-process syscall tally on the systemsyscallsbypid.stpprometheus process syscall tracepointThe syscallsbypid.stp script tallies each syscall for each running process. This information can be useful to determine the activity of various processes on the system. The script makes the information available via procfs in Prometheus readable format. When a process exits its data will be eliminated from the prometheus output. To avoid exceeding the storage limitations of SystemTap older entries maybe overwritten by newer entries. This can lead to some active process syscall counts disappearing and/or later reappearing with a lower value. Also note that the script does not properly name syscalls for 32-bit applications running on 64-bit machines.profiling FF7r processes 2 fs8tocol7vided8queue8received6 lated9 mote:quest?1s=iring1  transmission 3 oom2(t7un>s9 ' cript@1s:econds6en;7nd2ing1t1 rver 5 how@ing;imilar2ple1ular9k2ocket<s 9 top <$rted9"urce1"pace2 tamp2 rt2t@istics5 op2ped>/pg1 ream2ummarize<y 4ystem4  task@ cp;2   ipstat9hat 6$ "N ( -QTrace process exec() with command line argument details (non-debuginfo)execsnoop-nd.stpioThis can identify if CPU is consumed by short-lived processes, by tracing new process execution. It works by tracing exec() from the fork()->exec() sequence, which means it will not catch new processes that only fork(). It will also show every exec(), including those if a process re-execs.lwtoolsQ' -]Trace kill() signals showing process and signal details (non-debuginfo)killsnoop-nd.stpioThis traces signals system-wide, including those sent by the kill(1) command, and shows various details.lwtools[&s3Count syscalls with process details (non-debuginfo)syscallbypid-nd.stpioThis traces syscalls system-wide, and produces a summary report showing their counts by process ID, process name, and syscall types.lwtools oQbwhere ' ther ich %leill+E1 0i.th/V*Ub R ritebackss(ingx86yesJ HH5(nmessagek icrosecondsnC1nor bonitor a  ingasestcnameb -Jfs i umberi  &" olbservedlsnccuros bf6a    & n2a  ejpennednsslg  rationsn#Ar bderl therhutc4put i s bpairn6 renthesesnLticularoer aiodmicpidnEresumedhintkingasc 3ocess#b    eshfilingividesjrawfeadb 8ingms b  sonccent a ordaporte se%schedulecsj @ @> siReport opened files whose names match a given regexregex.stpregexUses the regex functionality to detect opened files whose names match a pattern given on the command line. If no command line parameter is given, demonstrate by filtering for files that end with an extension showing them to be an archive.general O)SystemTap python 2 support tapsetpy2example.stpsimpleA python support tapset that displays backtraces and variable values generalp -/Monitor Intel processors for throttling due to power or thermal limitscpu_throttle.stpprometheus limitsIntel processors have hardware mechanisms that will reduce the effective processors speed to avoid exceeding set thermal or power constraints. The cpu_throttle.stp script monitors when CPU throttling occurs and accumulates the amount of time in milliseconds that each processor is throttled. The script makes the information available via procfs in Prometheus readable format.generalkdsj# rets gtorfsfimple fomehrtedc paceeecifiedb ntnsl gtaph tisticsjusmpbaubmit c mmarizemppresseshwitchk filekyscalln s h ptema tapetabularpkesjllycen lxtualphatmeqa             mhseeisereadpspimeb  stampnAlsgo"a %p l tali3racenbackciol2oklffic g }}p0 370a ndcalls ombinationerrno ors xit frequently list most occurfnpidrocessesfiling videsreturnscripthowing orted tp ystemthewhich = m/[Trace processes running out of file descriptors rlimit_nofile.stplimitsThis script watches processes being scheduled and which try to allocate a file descriptor without luck.process' M![Print Resource Limits of Processplimit.stpprocessThe script prints a variety of resource limits for a given pid, like /proc/$$/limits on recent kernels.process e%7 Disable ptrace from Hierarchies of Processesnoptrace.stpprocess security guruBlocks ptrace(2) attempts from processes identified by stap -c/-x, as also specifiable from /proc/systemtap/stap_XXX/ control files. Processes may be added or removed from the blocked list.process[ ]-#Override default new-pthread stack sizesthreadstacks.stpthread guruOverrides default NPTL pthread_create stack size for all new threads created by target processes. Reports one line per process when the related glibc variable __default_stacksize is updated. Moot for glibc versions that support $LIBC_PTHREAD_DEFAULT_STACKSIZE_NP.process !!0\I<100 d250&mb"3 2eda4kb+512%64jifab- !  " ,- (+-$,"!), bout  U ccumulates iontiveLK[Iityually4dd0,7resses ll '{#.ocation s ongsoZYVnLdN <"R!Q !&ON6y6$ + pplicationM sgfcre)!guments ssociatedumedtvailable $#!erage ^,oid986 backtrace ssed   is"e"$#`!ingsttweenyonditfeb j4 Show Which Processes and System Calls Return Errors Most Frequentlyerrno.stpprofilingOn exit the errno.stp script provides a sorted list showing which combination of PID, system call, and error occur most frequently.profiling&3u-1 Display the Task Switches Happening in the Schedulersched_switch.stpprofiling functionThe sched_switch.stp script takes two arguments, first argument can be "pid" or "name" to indicate what is being passed as second argument. The script will trace the process based on pid/name and print the scheduler switches happening with the process. If no arguments are passed, it displays all the scheduler switches. This can be used to understand which tasks schedule out the current process being traced, and when it gets scheduled in again.profilingccepted?ing?tivity<ddress!4 +es7ll4ow<ong 4mong 4*)unt6n@cestry@ d@1     "(re9ttempts@ background> sed: e1cause2%en>ing2st 4tween8lock7 s2ridge7uffer2 y 4 %  tes 4('changes>+lient= ollected9s9mmand6 plete=uter?ngestion>nect@ion:  s ?tains7 ents7 inues2$unt 4'reation?wnd >daddr1"ta 4 ebuginfo1fault> stination1 isplay9s 5ns1*one: ++R"(0056T235X600R728S10\$0Y00\H2008R12T3Q4U5 V6S7W94Q3456V6074W7169UaY'ctivity]id0Qs(Qll ^owed\<mount\n ^*$dZ     re[verage\s ^@7 backtraceZ sZndHQsisYe\+havior`lock\ yY  tes ^"%callZn\*se\?s\(useZsZ ingZommand\Mpletion\utes\ nfigurable[tains ^1+ended[unt ^7-ve0Qdata ^    efault\8scending Z,vY QQ+- ;/]Monitor which executables use ioctl syscalls and what kernel code is handling the ioctlioctl_handler.stpprofilingThe ioctl systemcall is used to manipulate devices setting or special files. The way that ioctl syscalls are handled depend greatly on the device the special file is associated with. Using strace to monitor the open and ioctl syscalls may not give a good indication of what kernel code is actually handling the ioctl operations. The ioctl_handler.stp script is designed to provide more details. On exit the ioctl_handler.stp script provides a count of the ioctl syscalls for each executable run on the system. If there was some special device driver code used to handle to the ioctl, the output will have a tally of the times the function name and module was called for that executable. The "--all-modules" option should be included on the command line so the script can provide function name information.profiling yb0 491and$sbased estrokencpusdownevery five unctionsitkernel%list occupyingf"ut percentage!rintsofileing sampling criptecondstsortedtp theread sime s opwentyupser#with ZZAKa);E)Tally the Number of User-Space QEMU Eventsqemu_count.stpvirtualization qemu kvmThe qemu_count.stp script tallies the number of times each of the user-space qemu probepoints is encountered. When the script exits, it prints a list of the number of times each user-space qemu probepoint is encountered.virtualization_Jy#Ai)Tally the Number of User-Space QEMU IO on Each IO Portqemu_io.stpvirtualization qemu kvm ioThe qemu_io.stp script tallies the number of times each of the IO port on the guest virtual machines is touched by a input or output operation. When the script exits, it prints a count of the number of times each IO port read and written.virtualization QQ,\codeBYlinHlectFumnG mmandB,7LpilationF _ingF2letesF/ulsoryLFnnectedD%sideredD#tentionLs CvertFunt J%urrentG'veNdata BQefaultCltaB termineFg^isplaysC maxstringlenC5oesIsropA#pedAingAsAueLrationI:each'B (  ! iducationN    laborationFVpsedF ementB$mergencyNnableL,d E  counteredG7oughC"tryB&ventG/sG( ryM/xampleIceededL`ssive L ecutingEonEitB8"sA9+!plicitlyI{fileBndingDrstB%8veM0xingIollowedB)@B T,I?Profile Kernel/User Backtracespf4.stp_best profiling backtraceThe pf4.stp script sets up time-based sampling. Every five seconds it prints out a sorted list with the top twenty kernel and/or user stack backtraces (on a per-cpu basis). Use any of --ldd, --all-modules, -d MODULE, -d /PATH/TO/EXEC to add more symbolic info.profiling &&W42spent  tacksizemped p te&ssealingp`ufferingmmary pport$ymbolscall s !tem   callstaptablesrgetsk  hat% /#Oeq        ief s+ read s tacksough ime# <s1tampo7 /   race point  s sk  sy underlyingpdatedrobessed / ful ""[:0 A.K3H1FQ4634P9H2 FUT011H5O6N8P3FX8IV4F1.5195N6IU5536C67547Oa6A( - N ! -boutI ctuallyFddressD idNsNllA (ocationH sHmdIf$ountF$!- wnI%alyzedFeingHd6B. [&H/)0B pplication FsEre!AjgumentsL#sLciiC utomaticallyI]verage IFS backtraceL sL-TndNeA%!"denL5stItweenG#ig L GklL    logH othCyB* ACcBalledBnA$.c\ usingLlientD sD AA<|passingC2erM iodicallyDsMhp EidB0ortJ sitiveA)revious B%%intC);/7ed L5sB-#%obepointK& sKcess L3JesLL 2orI sIgtocolA sAvideFqemuJreachedLAdJ.sonIsIcentDferenceNquestsDireM,dFHsF, spectivelyB9ultingFaunningIbs B criptJA  !%3D econdGCZsM1urity$N rializationLverDiceIhouldA2imilarM^nceGocket Bpace Jecified A <ntMctampLgpFrtedGupGteI|isticsD s M epsGillD$ !!\<shown$%s"ignal's'mple!ze# low"er"ocket% urce-torage$p\!udy$,uch.ffered "/*mmarize+y &  ync "  hronous"scall% bypid&s&tem"+&s ""tap! tcp- dumplike-han"t"$eG#        ir") $ n!se"&!is8"ose '.read#shold"ime"*%o#   race"point # s("ing"( #ffic -nsmit/ wo "ypes&udp- ##Z081?2a?9  (  ccumulated"tivity*uallyddedll  ocate ongso  mount  nalysisd4', / yrerays%s  t tachesemptsuditbt backtrace  s sede.ing sttween  5lockedsy"  c2  !allsn -usedhildren>ompetingntention roluntspu  reated ingonycle s default scending riptor s ignated tinationtermine  isablepatch Y+Y7 k-/?Watch a Kernel Symbol Using Breakpoint Hardwarehw_watch_sym.stpmemory watchpointThe script will watch accesses to the starting address of a single kernel symbol and prints a traceback each time the symbol is accessed. This script needs to be run as root to allow access to the breakpoint hardware.memory{7sLog the kernel collapsing normal pages into a huge pagehugepage_collapse.stpmemoryThe kernel may attempt to group many normal sized pages into a single huge page to improve TLB performance. This operation may take a significant amount of time and affect program performance. You can identify if huge page collapse operations are occurring with the systemtap hugepage_collapse.stp script.memoryQ_-)Overview glibc malloc internal operationsglibc-malloc.stpmemory processThis script reports on internal statistics of the glibc malloc implementation, as used by a process restricted by stap -x/-cmemory "40 788a*ll7ndrgumentIbe3tweenPcanCollectmpiled4dataisplaysentry xpire frequencyt+om)unction>inNdicateKtervalMkernelleast-ist!modules8st*names?eeds1umericalHobserved%fn   ption9ally@utputRperiodic rintingQoduce;filing script econdsOhoworted tp ystem the  isAimer so   race point usedEsvariouswith5 >#m//Watch a Kernel Address Using Breakpoint Hardwarehw_watch_addr.stpmemory watchpointThe script will watch accesses to a single kernel address and prints a traceback each time the address is accessed. This script needs to be run as root to allow access to the breakpoint hardware.memory>[#}Show Paths to Kernel Malloc Invocationskmalloc-topmemoryThe kmalloc-top perl program runs a small systemtap script to collect stack traces for each call to the kmalloc function and counts the time that each stack trace is observed. When kmalloc-top exits it prints out sorted list. The output can be filtered to print only the first N stack traces (-t), stack traces with a minimum counts (-m), or exclude certain stack traces (-e).memory &&W 2stpmA ringsCystem AtapC Ftable I"9$sM3kes Fs!ingMllies JyJcpAextF hatA0LA%+ eA   .              mL0reFiirdG+sB',oseDime1B!- / f1 sF2 ! GoA"(GolAtalI9uchedJrace)BnpointIqsHing EkDs DfficCwo L"2ypeIudpAntilA5pIseH dL*rA7 ;sFing EvalidAueA,riousG erbumH c#Generate Log of Major and Minor Page Faultspfaults.stpmemoryThe pfaults.stp script generates a simple log for each major and minor page fault that occurs on the system. Each line contains a timestamp (in microseconds) when the page fault servicing was completed, the pid of the process, the address of the page fault, the type of access (read or write), the type of fault (major or minor), and the elapsed time for page fault. This log can be examined to determine where the page faults are occurring.memory T@T" +'YTrace slow file system synchronous reads and writes (non-debuginfo)fsslower-nd.stpio filesystemThis dynamically traces two common file system functions: do_sync_read() and do_sync_write(), and shows details of each call that is slower than a threshold. Many, but not all, file systems and workloads use these functions. Tracing their time provides one view of suffered file system latency.lwtoolsF!K)% SystemTap "Hello World" Programhelloworld.stp_best simpleA basic "Hello World" program implemented in SystemTap script. It prints out "hello world" message and then immediately exits.general O)SystemTap python 3 support tapsetpy3example.stpsimpleA python support tapset that displays backtraces and variable valuesgeneral=/##Hack the keyboardkeyhack.stpsimple guruThis script makes it appear that one's keyboard is broken, by changing keycodes at the kernel device driver level. Annoy your friends!general zc5 System-Wide Count of Syscalls by Executablesyscalls_by_proc.stpsyscallThe script watches all syscall on the system. On exit the script prints a list showing the number of systemcalls executed by each executable ordered from greatest to least number of syscalls.processTyg%System-Wide Syscall Statistics with FilteringsyscalltimessyscallCombination shell/systemtap script to measure system call counts and times. Can be filtered by process IDs, process names and users.process[xC%+9Tabulate System Call Errorserrsnoop.stpprocess syscallPrints a periodic tabular report about failing system calls, by process and by syscall failure. The first optional argument specifies the reporting interval (in seconds, default 5); the second optional argument gives a screen height (number of lines in the report, default 20).process }}8=-+'Profile Kernel Functionsthread-times.stp_best profilingThe thread-times.stp script sets up time-based sampling. Every five seconds it prints out a sorted list with the top twenty threads occupying the CPUs, broken down as a percentage of user and kernel time.profilingf7o)+Show Reasons and Durations for Processes Sleepinglatencytap.stp_best profilingThe latencytap.stp script collects data on the intervals processes are deactivated (sleeping). The script categorizes the reasons for the sleeps by analyzing the backtraces and displays a sorted list of the top 20 causes from largest total sum time sleeping to smallest. The output is updated every 30 seconds. The script needs to be compiled with the '--all-modules' option to produce reasons for sleeps caused by modules. Optionally, this script can be used with the '-c' or '-x' options to focus on a specific PID.profiling &&W2lockL GWing Ls Lg GngMmachineIsJdeDnuallyA8rkersE ximum IJV stringlenCyCemoryH  icrosecondsB"MghtD! llisecondsFGnimum ICModuleF8(ultipleFrocessorLnameB-?0etBfilterAwork#A werIXfs DdDot C teF"secondsL?umber&A0 ! =EofaA$  - %   &  ! lderIinFR( ceL1eL&lyN   peration I' sDtionC9NDalL(rA#D"_derC'gHutB<.6putJpacket A sA %geI!rameterIxsingFOss F0esF(  ]3>printsoc eduress es&($5or@ s6ducethread#racequeue$ingreadable centordlatedmovedports sourcelimitunnable#ing Ds  chedtimes uledr  ript: ecurity nt  s%haredlibort"wing 8igkill nal szesleepingome pace ecifiablec : )ed <ynds5      # nre Zis"C < ;< 9osereshold%us-ime-"U  /$s&&"oo`% - $( '@!- $)%4p sys talT racepoint s  kiggersNwenty o unexpected4p se #*d! ]ful$r spacesing ualvalueYXUrious ia%$"rtualmwarmupnsTs[yhat 0en$+7*J( b1 yShow performance ratios using perf.counter to access performance countersperf.stpprofilingOn exit the perf.stp script provides a sorted list showing cycles per insn, branches per insn, and cache refs per insnprofiling~0G5sProfile Kernel/User Functionsfileline-profile.stpprofilingThe fileline-profile.stp script ends by printing out a sorted list of the top twenty kernel and/or user processes providing file:line information, if available, from the samples addresses gathered over the time period the script is run. Use any of --ldd, --all-modules, -d MODULE, -d /PATH/TO/EXEC to add more symbolic info. To include the symbol name in the output, specify guru mode (-g) and add symbolname="yes" to the stap command.profilingetdev/work.% w(fs.!d 0on"     t" umber, o#f*"   n#    e ",'ly(%pen)ed)snoop)rations.r#1  ut ! liers$0put#packet- s-ssive%orts-rints ! ocess##es( duces&ing+gram!vides"+ &queue#)re(2ad"    s"ceive/ d-mote. ved0ing0port& s*quest##q#un0wtime+script! econds,nt' quence(rver0 "hort( w %* ing%  ''?]iPeriodically Print IO Activity by Process Nameiotop.stpioEvery five seconds print out the top ten executables generating I/O traffic during that interval sorted in descending order.io\i''Average Time Block IO Requests Spend in Queue ioblktime.stpioThe ioblktime.stp script tracks the amount of time that each block IO requests spend waiting for completion. The script computes the average waiting time for block IO per device and prints list every 10 seconds. In some cases there can be too many outstanding block IO operations and the script may exceed the default number of MAXMAPENTRIES allowed. In this case the allowed number can be increased with "-DMAXMAPENTRIES=10000" option on the stap command line.io [1'qCount I/O Syscalls using Alias Suffixesalias_suffixes.stpio statisticsalias_suffixes.stp is a demonstration of how alias suffixes in the systemtap language might be used. The script tracks the wall clock time for each invocation of the system calls open, close, read, and write. When the script exists it prints out the minimum, average, and maximum times in microseconds for each system call, followed by a count of times that each syscall was invoked and a histogram showing the distributions of times.generalqQ)W'Interactive Count Specified Eventseventcount.stpinteractive statistics thread processThe script periodically prints a count of specified events and their related tid's over the course of execution. Numerous configuration options exist to control filtering / reporting, some of which can be modified at runtime. See the script source for more information.general |p[7#Trace slow vfs opens.slowvfs.stpio simpleThis script prints a line for every kernel vfs_open operation that takes longer than a configurable number of microseconds. Highly contended or remote filesystems are likelier to hit this.ioZi3]Tally Backtraces for Inter-Processor Interruptscf.stpinterrupt backtraceThe Linux kernel function smp_call_function causes expensive inter-processor interrupts (IPIs). The scf.stp script tallies the processes and backtraces causing the interprocessor interrupts to identify the cause of the expensive IPI. On exit the script prints the tallies in descending frequency.interrupt A( 1WwProvide a per-process accumulation of syscall latency on the systemsyscalllatency.stpprometheus process syscall tracepointThe syscalllatency.stp script accumulates syscall latency for each running process. This information can be useful to whether excessive time is being spent in particular syscalls on the system. The script makes the information available via procfs in Prometheus readable format. When a process exits its data will be eliminated from the prometheus output. To avoid exceeding the storage limitations of SystemTap older entries maybe overwritten by newer entries. This can lead to some active process syscall error counts disappearing and/or later reappearing with a lower value. Also note that the script does not properly name syscalls for 32-bit applications running on 64-bit machines.profiling YOK/'1cve-2015-7547 security band-aidcve-2015-7547.stpsecurity guruhistorical emergency security band-aid, for reference/education onlysecurity-band-aidsNK/'1cve-2016-5195 security band-aidcve-2016-5195.stpsecurity guruhistorical emergency security band-aid, for reference/education onlysecurity-band-aids$Mg'9Per Process Statistics on Big Kernel Lock Usebkl_stats.stplockingThe bkl_stats.stp script can indicate which processes have excessive waits for the Big Kernel Lock (BKL) and which processes are taking the BKL for long periods of time. The bkl_stats.stp script prints lists of all the processes that require the BKL. Every five seconds two tables are printed out. The first table lists the processes that waited for the BKL followed by the number of times that the process waited, the minimum time of the wait, the average and the maximum time waited. The second table lists has similar information for the time spent in holding the lock for each of the processes.locks $$YM6 mmwriteback odeEule*t&1s(|$/mentsnitor #ing;s re: 1B-8st -ust name bar^?eed^werEDBonrmal*t`_*\e[ZWiceable>umberH YobjectccurfT;  >!= '-%/!!!' lder@?=nB, O O 3/-Nepen%rations 8tion e}allyr)9SR Oiginalut put76h4Bver "writtenCB@wing+page )"s  =rticularth,(3dflusher iod  % %via 3,(walkl clocks3tchdog hat EenKreich &le 1ose  ill 0th" in 7your oo undesirableps+ed rspaceing values   riable  ouswatcherboseia)ew wallsBtchhen&everich(le3ythefailith  Fin9rite , %yourzing !!\<in# "&.(# formation 1<put*tel ractive o verseocations(.+5 ,0t  keep rnel / yboard  )levelibrary fegamemits ne stedoaded cal tions !makes /(tch  ximum&zeechanism s mory icrosecond  s $) lliseconds #'seconds$nimum#odernulenitor ings re;phesuchltiple names    noseconds&ested 6o t/e'occur 0s Qf(+$ 5 n# ly ,pened rationPtional r ut!;put*para meter  s  J`$JUK/'1cve-2014-7169 security band-aidcve-2014-7169.stpsecurity guruhistorical emergency security band-aid, for reference/education onlysecurity-band-aidsTK/'1cve-2012-0056 security band-aidcve-2012-0056.stpsecurity guruhistorical emergency security band-aid, for reference/education onlysecurity-band-aidsSK/'1cve-2016-0728 security band-aidcve-2016-0728.stpsecurity guruhistorical emergency security band-aid, for reference/education onlysecurity-band-aidsRK/'1cve-2008-0600 security band-aidcve-2008-0600.stpsecurity guruhistorical emergency security band-aid, for reference/education onlysecurity-band-aidsQK/'1cve-2013-2094 security band-aidcve-2013-2094.stpsecurity guruhistorical emergency security band-aid, for reference/education onlysecurity-band-aidsPM1'1cve-2018-14634 security band-aidcve-2018-14634.stpsecurity guruhistorical emergency security band-aid, for reference/education onlysecurity-band-aids ""[N:pf3 4 ollingssiblyreviousint (ed*ing sobe sWcess9 D #" ""  "es"/fs&%#fileingXgram4sBmetheus('%perlya`]videAJsKingreadable)(&ppearingUTQcentursiveportsquestedstricted FunU)ning! _ ^K [s#amples ing   criptaD @6@%=??#econds  nsitiveAts ting hould~w  [UBg-)Trace Functions Called in Network Socket Codesocket-trace.stpnetwork socketThe script instruments each of the functions in the Linux kernel's net/socket.c file. The script prints out trace data. The first element of a line is time delta in microseconds from the previous entry. This is followed by the command name and the PID. The "->" and "<-" indicates function entry and function exit, respectively. The last element of the line is the function name.network"A]15System-Wide Network Packet Dropping Toolnetfilter_drop.stpnetwork packets guruThe script drops the specified number of packets of the specified protocol. Valid protocols are TCP, UDP, or ALL. If ALL is specified, all incoming packets are dropped. The number of packets to drop can be specified with a positive integer. A value of 0 indicates that packets should be dropped until the user manually exits.network   |1!7Trace system callsstrace.stp_best process syscallThe script loosely emulates strace, when applied to individual processes or hierarchies (via -c/-x), or the entire system (without -c/-x). A few output configuration parameters may be set with -G.processh{g%;Monitor Changes in Processor Executing a Taskchng_cpu.stpschedulerThe chng_cpu.stp script takes an argument which is the executable name of the task it should monitor. Each time a task with that executable name is found running on a different processor, the script prints out the thread id (tid), the executable name, the processor now running the task, the thread state, and a backtrace showing the kernel functions that triggered the running of the task on the processor.process 3*{9WmProvide a per-process syscall error tally on the systemsyscallerrorsbypid.stpprometheus process syscall tracepointThe syscallerrorsbypid.stp script tallies syscall errors for each running process. This information can be useful to whether there are excessive errors for various processes on the system. The script makes the information available via procfs in Prometheus readable format. When a process exits its data will be eliminated from the prometheus output. To avoid exceeding the storage limitations of SystemTap older entries maybe overwritten by newer entries. This can lead to some active process syscall error counts disappearing and/or later reappearing with a lower value. Also note that the script does not properly name syscalls for 32-bit applications running on 64-bit machines.profiling + 3C9Monitor capabilities and syscalls used by a process and it childrencontainer_check.stpprofiling container syscallThe container_check.stp script monitors the use of linux capablities and optionally forbidden syscalls by a process and its children. On exit the script prints out lists showing the capabilies used by each executable, which syscall used specific capabilites for each executable, a list of forbidden syscalls used, and details on any syscalls that failed during monitoring. This script is designed to help diagnose issues caused by restricted capabilies and syscalls when running an application in a container. If the script warns about skipped probes, the number of active kretprobes may need to be increased with "-DKRETACTIVE=100" option on the command lineprofiling _-Bmays;easurey icrosecondsqgratetstiontF `PDthe +   $    $~Oshowingize $kippedVlabub ome KJ\Hrted* paceecial Dfic(yCndstXtackp  Mtisticsorage<;9pz<race!ummarizepposedly.ymbol>ic2.9nameIscall'IH&E errorsbypid latency s"Jb#+_bypid tem0  X call s tap?><table)kes .ingllies yFlhan (t0K\#[8jX '?'>=U)uTrace NFSD requests with file names.nfsd-trace.stpnfs traceThis script traces all nfsd server operations by client_ip address, operation, and complete file name (if possible).networkT<u)Periodically Summarize Socket Activity on the Systemsocktopnetwork socketThe socktop script periodically prints out a list of the processes with the highest socket activity. Command line options for the script allow filtering to focus on particular types of sockets. The "-h" option lists socktop script's filtering options.network>;c77ASystem-Wide Count of Network Packets by IPsnetfilter_summary.stp_best network trafficThe script watches all IPv4 network traffic on the system. On exit the script prints a list showing the number of packets sent along source IP address / destination IP address pair encountered, and the total number of bytes sent among the pair. The list is ordered from greatest to least number of packets seen among the source/destination pairs.network A)cwWhy did the function fail?whythefail.stpspeculation monitoring function trace _bestThe whythefail.stp script prints a statement-execution trace for a given function, but only for those runs of the function that ended up with a (configurable) post-return condition.general,3#+mBad Filename Filterbadname.stpfilesystem guruThe badname.stp script shows how one could prevent the creation of files with undesirable names using guru mode.generaltQ/)UTrace Socket Activity of a Processsocket-events.stpsocket syscallPrints the life cycle of all sockets associated with a process. This includes bytes and timing. The timing information that is tracked includes event completion relative to the start of said event and the end of the previous event. Currently tracks read, write, recv, send, connect and close.generalodulenitortings }stvname$q! )synosleep q ot t> %et7w{1umberu3%of=q8  &6 ft-n"q  ( perations } tionalxsv(r t< derr edzutq'put|ver} parameters|enthesesq#ticularu erformanceiodicxallyvidq' $rintr edt"!#sq&oc ressq%   ess  or t,# stmod topv !!\ <1 23 aS _ -!7 ctive"itys)ggregate dWYlias  l ows{nbd*!:  $ ersonnoysi yppearreo@gument  /snranges s%;sociated t #vailable erage c/gd backtraces dnamesed ise.0!ing1st tweenroken ut y : tescall8graph!   s n hangesinglickockse 1 "ode lor s mbinations pilationlete ion ncurrently3dition figurable tionnect/text 0LWmTracing Contention on Big Kernel Lockbkl.stplockingThe bkl.stp script can help determine whether the Big Kernel Lock (BKL) is causing serialization on a multiprocessor system due to excessive contention of the BKL. The bkl.stp script takes two arguments. The first one is optional, and used to enable backtraces, and print them once a process has been holding the BKL for a user specified number of nseconds is reached. The second option is compulsory and is the number of processes waiting for the Big Kernel Lock (BKL). When the number of processes waiting for the BKL is reached or exceeded, the script will print a time stamp, the number of processes waiting for the BKL, the holder of the BKL, and the amount of time the BKL was held. If backtraces are enabled, a backtrace will be printed as well.locks kk'5{make keyboard noiseskey.stpsimpleFor fans of Leroy Anderson and Typewriters only, this script arranges to play a click or a zing for various keystrokes.generalYA!/7Print the Size of a C Typesizeof.stpstatistics memoryThis script prints the size of a type, based on dwarf debuginfo for any kernel or userspace module, or trial-compilation of a given header file name.general Y9GUInteractive Print the Size of a C Typesizeof_interactive.stpstatistics memory interactiveThis script prints the size of a type, based on dwarf debuginfo for any kernel or userspace module, or trial-compilation of a given header file name. Types and corresponding locations are provided to the script at runtime via keyboard input. The format of the input is identical to that of sizeof.stp (see script source for more information). Types and locations can be repeatedly given until the process is terminated. general g>0 345abased every five unctionsitkernellistoutpf2 rintsofileing samplesing cripteconds tsortedtp tenheimeopupwith yFyJg I'=Capture SSL/TLS master secrets from gnutls and openssl userscapture_ssl_master_secrets.stpio monitoringCapture SSL/TLS master secrets from gnutls and openssl users for easy traffic decryptionioVf %?cMonitor Read/Write of the Boot Sector Area of Block Devicesmbrwatch.stpio monitoring disk simple The mbrwatch.stp script reports any attempted reads/writes of the first few sectors of a raw block device.iofeY!+GReport an disk out-of-space condition.enospc.stpdisk filesystemThis script monitors a filesystem implementations for early internal indications of ENOSPC, and reports these to the system logger and the systemtap console.ioudY+uMonitoring Attribute Changes to a Fileinodewatch2.stpio The inodewatch2.stp script outputs the executable name, process id, and attributes each time the attributes are changed on the specified inode on the specified major/minor device.io ""[ :controluld  -0,nt <rsereation  urrent5ly)ycledataXebuginfo  monstrationviceidfferentsplayAed]s  tributionsIriverwarf each  nable+d $H1edtryvent  %counts xecnameutableing on  ists)pressionfailnsifthM"lenamesystemteringrst veollowed9r4 %  )maturthD) requentlyiendsunction  s ' topgeneralP ttimeofday*iven  roupinguru   xxz0 88720#302a;ll<nalyzingdre backtracese8sty0cOanJ tegorizesusedDs$ollectsmpiled9data eactivated isplaysurationsevery1focusTr0rom% intervals s/largest&tencytap istmodules= needs6of nOption>allyGsRrPutput.pidXrocesses duce@filing reasons0script  'econds3howleepings/mallest,ortedpecificWtp um(the   isHime)o + p"tal'updated0sedLwith:xQ  %security`Qek`s`howing` imple[zed`low[vfs[mpZome\'rted]pend\tap\LpbQ uccessfully ^  m ^ ystem ^takes[lliesZyZen] han[t[  eFY      re\)is [>ime\ oZ&&o\,p]tals ^>5race[ks\ffic]vfs[ waiting\ ith\Frites ^<3ing^ten^% 66mO#QSummarize Disk Read/Write Trafficdisktop.stpdiskGet the status of reading/writing disk every 5 seconds, output top ten entries during that period.io6le#sTrack Cumulative IO Activity by Process Nametraceio.stpioEvery second print out the top ten executables sorted in descending order based on cumulative I/O traffic observed.iopk-)Switch log filesswitchfile.stpioEvery second print a log message and switch log files every 5 seconds.io {e-aShow Attribues in Table for ansi_set_color()ansi_colors2.stpformatThe script prints a table showing the available attributes (bold, underline, and inverse) with color combinations for the ans_set_color() function in the ansi.stp tapset.general +OSee the amount of wall clock time a process spends in various statesstopwatches.stptimeThe stopwatch.stp script illustrates how to use multiple stopwatches record how much wallclock time a process spends in kernel- and user-space. On exit the script prints out the time in seconds, milliseconds, microseconds, and nanoseconds. Note that this output of this script is not directly comparable to the time command because time records the time that the process is actually active in kernel- and user-space.general y4yjI+/#IO Statistics for SCSI Devicesiostat-scsi.stpio profiling scsiThe iostat-scsi.stp script provides a breakdown of the number of blks read and written on the machine's various SCSI devices. The script takes one argument which is the number of seconds between reports.io"iy1%Tally the Number of NFS Functions Used by Each Processnfs_func_users.stpio profilingThe nfs_func_users.stp script counts the uses of NFS functions in the kernel on a per process bases. The output is sorted from the process with the greatest number of NFS functions called to the least. The output contains the executable name, the process number, and the total number of NFS functions called by the process.ioIh'');disable fsynceatmydata.stpio guru simpleSuppresses fsync() syscalls from processes identified by stap -c/-x by turning them into presumed-faster fsync() on some dummy or other file descriptorio  +oyTrack IRQ's and Other Processes Stealing Cycles from a Taskcycle_thief.stp_best process scheduler time tracepoint interruptThe cycle_thief.stp script instruments the scheduler and IRQ handler to determine which processes and interrupts are competing with the specified task for the cpu cycles. This script uses the '-c' or '-x' options to focus on a specific task. The script output the number of times the task migrates between processors, histograms showing the length of time on and off processor, lists of processes running while the task is off the processor, and the interrupts that occurred while the task was running.processi O5Ipthread mutex contention analysismutex-contention.stplockingTracks pthread-mutex initialization/use and underlying futex operations, to identify (with backtraces/symbol-names) the mutexes suffering most contention. Invoke with "-d SHLIB --ldd", perhaps with -DMAXMAPENTRIES=NNNN for some large NNNN, if the arrays overflow due to heavy activity.process