<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - RFE: Collect Python backtraces" href="https://bugs.freedesktop.org/show_bug.cgi?id=82507#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - RFE: Collect Python backtraces" href="https://bugs.freedesktop.org/show_bug.cgi?id=82507">bug 82507</a> from <a class="email" href="mailto:filak.jakub@gmail.com" title="Jakub Filak <filak.jakub@gmail.com>"> Jakub Filak</a> <pre>(In reply to Zbigniew Jedrzejewski-Szmek from <a href="show_bug.cgi?id=82507#c5">comment #5</a>) > > and how to let ABRT collect additional information about crashing processes. > > What additional info? > For example, we might need to join process' user and mount namespaces and run rpm there to get packaging information. We usually gather packaging information post-mortem but this is impossible if the process was the only process in its namespaces. > > Moving systemd-coredump from systemd's repository to its own repository would be appreciated too. > > Why? Do you need faster releases? ABRT team will definitely want to contribute to systemd-coredump and building entire systemd is a bit slow and complex. Another point is that systemd-coredump & coredumpctl uses systemd internal functions and that might make patches harder to backport to older releases (we have some legacy customers). There might be a problem to install & test our changes due to conflicts with the installed systemd. And there are probably more points. However, this is not a must. I would be just happier if I were not forced to patch systemd :)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>