https://github.com/raspberrypi/firmware/issues/377#issuecomment-84022356
> vcdbg doesn't need to talk to VC for most of the commands. It opens VC's memory and extracts as much as it can, but does rely on finding some symbols from memory.

vcdbg log msg
vcdbg log assert
`vcdbg tx -v` requires a non-stripped ELF, which the rpi foundation doesnt release
https://www.raspberrypi.org/forums/viewtopic.php?p=1875343#p1875343
> "vcdbg log assert" needs to have "start_debug=1" in config.txt to report anything.



root@raspberrypi:~# vcdbg dumpstate 2>/dev/null


https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=195178&start=100
> What are the comparative loadings on the 2 VPU cores? "sudo vcdbg hist gnuplot" should give you two files called task.gpt and task.gpt, and "gnuplot task.gpt" should then display the three graphs of VPU0, VPU1, and combined.

`vcdbg hist gnuplot` shows VPU usage??

> Got the static vcdbg from pelwell's link:
> https://github.com/raspberrypi/Raspberry-Pi-OS-64bit/issues/67#issuecomment-653209729
a static vcdbg!


https://www.raspberrypi.org/forums/viewtopic.php?p=1827424#p1827424
> There is an alternative implementation of part of vcdbg that you can try: https://git.venev.name/hristo/rpi-vc-log