I am evaluating some ways how to properly implement reporting
a crash from the command line interface. User must be able to
describe the circumstances of the crash, edit the back trace,
and generally check which information is sent outside.
So the question is what happens when some user runs e.g.
$ abrt-cli --report df647e7771d228e2c281fafd8ca7047a2e34debd
So far, two ideas seems reasonable:
1) The application opens a text editor (specified by $EDITOR,
$VISUAL, or vi as a fallback) on a temporary file which contain
all the information (crash report).
However, there is a small problem with this approach:
abrt expects to receive information about crash
separated in certain fields (desc, backtrace, release etc.)
The temporary file contain all the fields merged, and the application
must separate them before sending the data over DBus.
I created an example crash report which shows how this problem could
be addressed. See attached report.txt.
2) Create ncurses interface with editable fields, just a single
screen for the purpose of crash reporting.
The former approach is probably better for experienced users,
just edit a file in your favourite editor and you are done.
Also `git commit` uses that. The latter approach is friendlier
to novice users. Nonetheless, inexperienced users will use
the abrt-applet and abrt-gui.
Which approach seems better to you?
Any ideas, suggestions?
Karel Klíč <kklic(a)redhat.com>
Developer, package maintainer
Office: +420 532 294 128
Mobile: +420 776 196 877
Red Hat Inc. http://cz.redhat.com