You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can teach abrtd to look for debuginfo not just in the downloaded database and not just in /usr/lib/debug/.build-id/, but also try contacting a debuginfod server. The latter would not require any abrt-side tracking or cleanup.
One bit of new code this would require is a thin python binding to the -ldebuginfod client library (3 or 4 simple functions). Would y'all be receptive to a simple ctypes FFI within your codebase?
The text was updated successfully, but these errors were encountered:
Please note that the Fedora debuginfod servers are now online. It may be that you can jettison your entire RPM downloading / indexing efforts, and just use
We can teach abrtd to look for debuginfo not just in the downloaded database and not just in /usr/lib/debug/.build-id/, but also try contacting a debuginfod server. The latter would not require any abrt-side tracking or cleanup.
One bit of new code this would require is a thin python binding to the -ldebuginfod client library (3 or 4 simple functions). Would y'all be receptive to a simple
ctypes
FFI within your codebase?The text was updated successfully, but these errors were encountered: