VUDEBUG(1)
π VUDEBUG π
okay so bestie, this is vudebug from the General Commands Manual β it's the debug utility for umvu, and it's lowkey iconic. let's get into it π«Ά
β¨ NAME β¨
vudebug β debug utility for umvu
π SYNOPSIS π
vudebug --help
vudebug [debarg [debarg ...]] [ -- command [args]]
where debarg has the following syntax:
+[tag[tag ...]][:colorspec]
or
-[tag[tag ...]]
or
?[tag[tag ...]]
and colorspec is a combination of the following characters: nwrgbcmyNWRGBCMY+-_*#
πΈ DESCRIPTION πΈ
vudebug turns debug log messages on and off, bestie. the log messages are sorted into categories, and every category has its own tag β and a tag is literally just one alphanumeric character. the convention (iykyk) is that lowercase letters are for logging messages coming out of the hypervisor, while capital letters are for modules. cute, right?
now here's the tea: when the vudebug command line ends with -- followed by a command and its command line arguments, then logging gets enabled for the execution of that command β and for all the subprocesses it eventually creates too, no cap. otherwise? vudebug just changes the categories to log globally, for all the processes. periodt.
π OPTIONS π
--helpβ print a short help message and exit. that's it, that's the whole vibe πdebargβ every debug argument starts with+,-or?, and then comes zero, one or more debug tags. quick rundown:+enables log messages β¨-disables log messages π?checks if the log messages are enabled π
when the debug argument has no tags at all, it gets applied to all the tags. and the fun part: log messages of different categories can be shown in different colors and font effects, because why would you debug in plain monochrome when you could be extra? π
when vudebug is used to enable/re-enable tags (+), each debarg can be followed by a semicolon (:) and a color specification. a color specification is a string composed by the following characters:
nwrgbcmyβ set foreground color (black, white, red, green, blue, cyan, magenta or yellow)NWRGBCMYβ set background color (black, white, red, green, blue, cyan, magenta or yellow)+-_*#β font effect (bright, dim, underlined, blinking, reverse video)
π₯ EXAMPLES π₯
get a list of available logging categories:
$ vudebug ?
D - VUDEV
F - VUFUSE
N - VUNET
a - ACTION
c - CHOICE
f - FILETABLE
m - MODULE
n - NESTED
p - PATH
s - SYSCALL
v - VNODE
heads up bestie: the list may vary depending on the version of the hypervisor and the modules currently loaded. so don't come for me if yours looks different π
enable path resolution logging:
$ vudebug +p
list some categories to see which ones are active:
$ vudebug ?ps
p + PATH
s - SYSCALL
PATH is active, SYSCALL is not active. noted. π
disable all the categories:
$ vudebug -
launch a bash and log syscall requests in red, path resolution in bold-blue, module choice in reverse green:
$ vudebug +s:r +p:b+ +c:g# -- bash
likeβ¦ the aesthetic of that one command? obsessed. π
π¦ SEE ALSO π¦
π AUTHOR π
VirtualSquare. Project leader: Renzo Davoli
and that's the whole page, bestie!! π«Ά this was VirtualSquare-VUOS, dated January 2024 β go forth and debug slayfully β¨π
π¦ where this page comes from
- debian trixie: vuos-cmds 0.9.2-1 Β· GPL-2.0-or-later
- ubuntu questing: vuos-cmds 0.9.2-1
- ubuntu resolute: vuos-cmds 0.9.4-1 Β· GPL-2.0-or-later
- ubuntu stonking: vuos-cmds 0.9.4-1 Β· GPL-2.0-or-later
- Copyright (C) 2019 VirtualSquare. Project Leader: Renzo Davoli
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms