ABRT duplicate detection - is it for real?
Karel Klic
kklic at redhat.com
Thu May 13 13:32:16 UTC 2010
Dne 13.5.2010 14:55, Christoph Wickert napsal(a):
> AFAIK abrt recognizes dupes based on hashes of the backtrace, but the
> format of the backtraces has changed with nearly every new ABRT version,
> so the backtraces will not be the same even from exactly the same crash.
The hash is not calculated from the whole backtrace, but from simplified
version of it. In the case of gwget
(https://bugzilla.redhat.com/attachment.cgi?id=374581), the input for
hash calculation looks this way:
$ abrt-backtrace ./backtrace -n -d 4 -r -m
Thread
node_get_last
get_sequence
IA__g_sequence_iter_get_sequence
IA__gtk_list_store_set_valist
Only names from the top few frames are used.
> How to deal with that problem? And what about more complicated cases,
> for example a backtrace where the commandline is different as
> in /usr/bin/program /home/user/some.file. As user and filename change,
> the hash cannot be the same.
The command line is not a part of the hash calculation. AFAIK only the
backtrace, package name, and a part of package version is.
Karel
More information about the devel
mailing list