Please create a human-readable backtrace file

[jfilak]

Create 'backtrace' from mini-debuginfo along with 'core_backtrace'.

[mmilata]

Won't the existence of backtrace confuse the rest of ABRT (e.g. workflows with local/remote retracing)?

Do you have any preference wrt format?

[jfilak]

Well, it might confuse ABRT in the future when we decide to not generate backtrace if it already exists, but the current implementation generates backtrace unconditionally whenever user reports an user space crash to Bugzilla.

In case we would like to avoid the future problems, we shouldn't definitely invent a new file (Can you imagine the absurdity of presence 3 files containing backtrace in 3 different formats?). So, what about to change core_backtrace's format from JSON to something human readable and easy parseable? (IIRC we have been there and it wasn't flexible enough and it was error prone).

Hmm, shouldn't we develop a tool/API converting core_backtrace into something human readable?

[mmilata]

I don't think we should change the format again, for the reasons you mentioned. If it doesn't confuse ABRT into sending the core_backtrace-based-backtrace to e.g. bugzilla then I'm for reusing the backtrace file.

Tool for converting core_backtrace to some gdb-like format is a matter of five lines of python:)