Hi -
If you never use debuggers, tracing tools, profilers, crash dump
analysis tools, go ahead and skip this note!
If you're still reading, you know you sometimes need debuginfo for the
packages you're working with. And you probably know that
% sudo debuginfo-install
is still the official way of getting at it. But did you know that we
have a better way?
DEBUGINFOD has been a part of elfutils since late 2019. It can serve
debuginfo and source code for your own or for other people's binaries
to a whole gamut of tools. (GDB 10 will include support too!) It
works across HTTP, no root, no manual debuginfo-install, no big
downloads, no big deal. There are even some public servers that have
some Fedora content already, as well as from other distros. This page
covers more about the client & server situation:
https://sourceware.org/elfutils/Debuginfod.html
You can try it today against our test server:
% export DEBUGINFOD_URLS=https://debuginfod.elfutils.org/
% export DEBUGINFOD_PROGRESS=1
% # $debugger-type-tool /path/to/program
% eu-stack -v -p $$
% stap -L 'process.function("*").call' -c /bin/ls
The problem is that Fedora itself doesn't run a server, and our test
server can afford to carry only a subset of debuginfo/debugsource rpms
& architectures. So, fedora developers / users cannot get at all the
info, or from an official source. I wonder if it's time to get one
set up. If there is interest, I'd be happy to start discussing
logistics with fedora infrastructure folks.
- FChE
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
