The OpenBMC debugtools tarball clashes with the filesystem layout of witherspoon systems, and contains a number of other outstanding issues with respect to the tools it deploys. The debug script here documents and executes the workarounds necessary to make it functional.
./debug [USER@]HOST TARBALL
For example:
$ ./debug root@my-witherspoon obmc-phosphor-debug-tarball-witherspoon.tar.xz
The script will:
- Ensure
/usr/local
is a tmpfs mountpoint (may not be if system is configured for Field Mode) - Deploy the debugtools tarball to
/usr/local
- Make
perf(1)
work by- Installing a fake
expand(1)
if necessary - Fixing the
objdump(1)
symlink - Disabling
perf(1)
's buildid tracking (fills the RW filesystem)
- Installing a fake
- Make
latencytop(1)
work by deploying and symlinking libncurses{,w}.so