Automatic problem management with anonymous reports

Jakub Filak df6ebbd78f Release 0.9 11 anni fa
docs 91340705b1 Documentation cleanup 11 anni fa
include ea6a01c698 include raw kerneloops text in uReport; closes #87 11 anni fa
lib 4e60d6b05d also fill kernel version in koops stacktrace - closes #105 11 anni fa
python f7eaee5f2e Build python api manpage conditionally 11 anni fa
tests fee8c6a30b fix module list parsing; closes #102 11 anni fa
.dir-locals.el 59b4badb3d Coding style for Emacs 13 anni fa
.gitignore 1c7c4f736d tests: refactor some common code 11 anni fa
.travis.yml 1f32b8854e travis: show testsuite.log if tests fail 11 anni fa
COPYING 6a3cb52d6b Initial commit 13 anni fa
Makefile.am 4280bf6220 Move public headers into separate directory 11 anni fa
NEWS df6ebbd78f Release 0.9 11 anni fa
README 91340705b1 Documentation cleanup 11 anni fa
RELEASE 875c0ee95f Release 0.8 11 anni fa
autogen.sh 6a3cb52d6b Initial commit 13 anni fa
configure.ac df6ebbd78f Release 0.9 11 anni fa
satyr.1.in a2601cce5f Include version string in the man page 11 anni fa
satyr.c a2acca9f7c Type-agnostic distance matrices 11 anni fa
satyr.pc.in 3b15a487b8 Btparser shared library renamed to satyr. 11 anni fa
satyr.spec.in df6ebbd78f Release 0.9 11 anni fa

README

Failures of computer programs are omnipresent in the information technology
industry: they occur during software development, software testing, and also in
production. Failures occur in programs from all levels of the system stack.
The program environment differ substantially between kernel space, user space
programs written in C or C++, Python scripts, and Java applications, but the
general structure of failures is surprisingly similar between the mentioned
environments due to imperative nature of the languages and common concepts such
as procedures, objects, exceptions.

Satyr is a collection of low-level algorithms for program failure processing,
analysis, and reporting supporting kernel space, user space, Python, and Java
programs. Considering failure processing, it allows to parse failure
description from various sources such as GDB-created stack traces, Python stack
traces with a description of uncaught exception, and kernel oops message.
Infromation can also be extracted from the core dumps of unexpectedly
terminated user space processes and from the machine executable code of
binaries. Considering failure analysis, the stack traces of failed processes
can be normalized, trimmed, and compared. Clusters of similar stack traces can
be calculated. In multi-threaded stack traces, the threads that caused the
failure can be discovered. Considering failure reporting, the library can
generate a failure report in a well-specified format, and the report can be
sent to a remote machine.

Due to the low-level nature of the library and implementors' use cases, most of
its functionality is currently limited to Linux-based operating systems using
ELF binaries. The library can be extended to support Microsoft Windows and OS
X platforms without changing its design, but dedicated engineering effort would
be required to accomplish that.