Miroslav Suchý <msu...@redhat.com> writes: > You do not need a crash for that > /usr/libexec/drkonqi --dialog --keeprunning --pid $PID > will try to debug running application. I tried that with PID of > running vim.
Nice, thanks. In the "Developer Information" tab, one can watch gdb "Downloading separate debug info for ..." lines, so the debuginfod machinery is working fine. (... except in the case of binaries that have been replaced since they started running, since drknoqi runs the child gdb, targeting /usr/bin/path name rather than /proc/$PID/exe.) (... and except that drkonqi advises "The generated crash information is not useful", though the backtrace info looks nice and complete.) - FChE _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
