<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#c2">Comment # 2</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>If you want to show detected uncaught Python exceptions in coredumpctl, why don't you teach coredumpctl to load that data from Problems2 D-Bus API[1] exposed by ABRT? Once you do that, coredumpctl would be able to show also uncaught Java exceptions, Ruby exceptions and basically everything ABRT detects. There is no need to re-invent/re-implement the error detection utilities. Or if you don't want to use the D-Bus API, why don't you ask ABRT team to write the detected exception data to journal too? We are working on it [2][3] because Cockpit team asked us for it. 1: <a href="https://jfilak.fedorapeople.org/ProblemsAPI2/index.html">https://jfilak.fedorapeople.org/ProblemsAPI2/index.html</a> 2: <a href="https://github.com/abrt/libreport/wiki/Reporter-systemd-journal">https://github.com/abrt/libreport/wiki/Reporter-systemd-journal</a> 3: <a href="https://github.com/abrt/abrt/wiki/systemd-journal-catalog-messages">https://github.com/abrt/abrt/wiki/systemd-journal-catalog-messages</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>