Debian Codegraph @

testsuite/systemtap.interactive/README

raw
1 systemtap monitor mode manual testing guide
2
3 Requirements:
4
5 Systemtap must be compiled with json-c and ncurses development
6 libraries present for this feature to work.
7
8 Testing steps:
9
10 1. Fire up a basic script:
11 # stap --monitor -ve 'global x = 0; probe timer.s(1) {println(x++)}'
12
13 - Check that the top window displays the module status and the bottom
14 window contains the module output. Make sure that the status window
15 displays the following information: uptime, uid, memory, module name,
16 the global variable x and its current value, and the current list of
17 probes.
18
19 - Manually resize the terminal to check that each of the ncurses windows
20 are also resized to take up 50% of the height of the terminal.
21
22 - Test all of the commands listed in the help page by pressing h:
23 - Pressing r should reset the global variable x to 0, the module
24 output should change too.
25
26 - Pressing s repeatedly should change the sorting attribute and
27 reorder the probe list accordingly.
28
29 - Pressing t will bring up the prompt to enter a probe index to
30 toggle. Enter the index for the timer probe we have created
31 and the probe's state should change to "off"; the module output
32 should also stop. Toggle to probe again to reactivate it.
33
34 - Pressing the u/d/pageup/pagedown keys should scroll the module
35 output.
36
37 - Pressing the j/k/down/up keys should scroll the probe list.
38
39 - Press q to quit the script and make sure nothing crashes.
40
41 2. Fire up a script with high activity:
42 # stap --monitor -ve 'probe vfs.read {println(1)}'
43
44 - Make sure nothing crashes and exit the script.