These load fast, but are hard to use for debugging or hacking. In case
you want to use the debug files then you can do the following. Keep in
mind they're *much* slower to load than the optimized files.
If you're hacking from the source tree ...
... then debug files will be used. You symlinked the code into
~/.local/share/cockpit and that code contains debug info.
[link to stef.thewalter.net
If you're building from source ...
... then use the --enable-debug autogen.sh or configure argument to
enable installation of debug files at install time.
[link to github.com
If you're installing from Fedora packages ...
... then install cockpit-debuginfo to use debug files.
If you're building packages ...
... and want to build your own debuginfo packages, then you can find
the debug sources in /usr/src/debug. Create a sub-package which installs
those files into /usr/share/cockpit next to the optimized files.
Poke someone on #cockpit if you run into problems.