The patches implement function fingerprinting for coredump-level backtraces as
described in . Note that it is not compiled by default, you need to pass
'--enable-dupcheck-fingerprint' to the configure script.
You can also checkout the branch 'function_fingerprints' from abrt git instead
of applying the patches.
Martin Milata (2):
a-a-g-c-b: Function for PLT parsing
a-a-g-c-b: Fingerprinting implementation
doc/abrt-action-generate-core-backtrace.txt | 8 +-
src/plugins/abrt-action-generate-core-backtrace.c | 906 ++++++++++++++++++---
2 files changed, 789 insertions(+), 125 deletions(-)
This patch set modifies GUI so that for non-IT users
abrt provides fewer screens. For developers, a somewhat
hidden option exists to see all data, all possible events
and run them in any order:
in abrt-gui, select "Edit"->"Open problem data".
This is called "expert mode".
To this end, report-gtk acquired a new option, -e EVENT,
which specifies which event(s) to run. Without -e,
we get expert mode.
To make behavior configurable, new events, report-gui
and open-gui, are used by abrt-gui and applet to start reporting,
or to do "Edit"->"Open problem data" thing.
If events are not defined, they fall back to direct execution
of "report-gtk $DUMP_DIR".
Open question is how to select -e EVENT options in lieu
of third-party analyzers or collectors...
Patches are tested to apply to current gits (with some offsets).
Preparatory libreport1.patch is already in git and thus is not attached.
Patches are run-tested. The intermediate libreportN.patch
patches show gradual changes as I massaged the source
into implementing new logic.