Kernel-Module based View-OS. KMview has the same features of UMview but it needs a specific kernel module to run. KMview is faster than UMview, and it overcomes all of the restrictions imposed by ptrace. KMview supports job control, debugging of code inside it (like strace) and real nested invocation. Working inside a kmview session means having all the features of umview ready-to-use while paying for a limited performance overload.
Kmview is not yet included in our Debian set of packets as it needs a Linux Kernel providing the utrace facilities (by Roland McGrath).
For further technical information about KMview please refer to the following documents:
The call syntax is about the same as umview. Some kernel optimization flags are missing because kmview uses its specific module to communicate with the kernel. The following part of this paragraph is almost cut+paste from the sibling page about umview, but we have copied the contents here (with kmview instead of umview) for the sake of completeness.
kmview is used to start a new command (passed as argument with it own additional optional arguments). Once started
if there's not any module loaded the command behaves like executing outside kmview. When starting a non-interactive shell program within kmview it may be useful to preload modules.
$ kmview bash
- module preloading
- preloaded modules can be specified with command line argument
kmview -p modulename[,param1,...,paramN]
$ kmview -p lwipv6.so,vd0=/var/run/vde.ctl bash
- additional features
- Module nesting is autodetected and enabled by default when available. It may be useful for debugging reasons to disable this options with flag parameters passed to kmview.
- disable modules nesting
$ kmview -x bash
- If kmview was compiled with debugging symbols enabled it is possible to redirect all the debugging output to a file specified in the command line.
$ kmview -o debugging_file.txt bash
KMview uses the same commands and modules described for UMview