<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - RFE: Collect Python backtraces"
href="https://bugs.freedesktop.org/show_bug.cgi?id=82507#c4">Comment # 4</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 <span class="vcard"><a class="email" href="mailto:filak.jakub@gmail.com" title="Jakub Filak <filak.jakub@gmail.com>"> <span class="fn">Jakub Filak</span></a>
</span></b>
<pre>(In reply to Zbigniew Jedrzejewski-Szmek from <a href="show_bug.cgi?id=82507#c3">comment #3</a>)
<span class="quote">> Yes, something like this. I'm experimenting with the systemd-coredump-python
> because this works without abrt running. So it has the same basic advantages
> and disadvantages that systemd-coredump has over abrt: does not require abrt
> to be running, works in early boot, only logs to the journal and does not
> provide any higher-level handling.
> </span >
ABRT is not running for fun - it deals with duplicates (you don't want to save
every coredump of a program crashing in a loop), it enforces disk consumption
quotas, it performs automatic actions, .... If ABRT hooks were just creating
records for detected problems, we wouldn't need ABRT running.
<span class="quote">> I think such a module might be integrated one of three ways:
> - an alternative to the abrt hook, to be used when abrt-addon-python3 is not
> installed
> - an alternative to the abrt hook, to be used until abrt becomes available
> - teaching abrt to read python backtraces from the journal
>
> The last option is the most interesting I think, but it only makes sense if
> abrt gets the general ability to read coredump entries from the journal in
> general, also for actual coredumps.
>
> The changes in #4526 are fairly generic, and should allow taking the same
> path for other languages (ruby, java, etc.). What d'ya think?</span >
I would tighter integrate ABRT with systemd, if you had a plan how to deal with
floods of new problems (corefiles appearing every 1ms) and how to let ABRT
collect additional information about crashing processes. Moving
systemd-coredump from systemd's repository to its own repository would be
appreciated too.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>