I encountered Xorg crash caused by qxl driver.  As the same time, there was already existing bug report from another crash from another cirrus driver.  Instead of creating new bug, ABRT added comment to the existing cirrus bug.

This was caused by the fact that ABRT did not filter out all unrelated function names from the data the abrt_hash is computed from.  Therefore two different backtraces (having only the error handling really common) resulted in same abrt_hash.


Version-Release number of selected component (if applicable):
abrt-2.1.12-2.fc20.x86_64


If you want to see the backtraces:

  * attachment 862417 [details] is for the "cirrus" bug 1064466
  * attachment 865735 [details] is for the "qxl" bug 1067709

~

The part of stack that is common:

#0  0xXXXXXXXXXXXXXXXX in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#0  0xXXXXXXXXXXXXXXXX in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0xXXXXXXXXXXXXXXXX in __GI_abort () at abort.c:90
#2  0xXXXXXXXXXXXXXXXX in OsAbort () at utils.c:1328
#3  0xXXXXXXXXXXXXXXXX in ddxGiveUp (error=error@entry=EXIT_ERR_ABORT) at xf86Init.c:1097
#4  0xXXXXXXXXXXXXXXXX in AbortDDX (error=error@entry=EXIT_ERR_ABORT) at xf86Init.c:1141
#5  0xXXXXXXXXXXXXXXXX in AbortServer () at log.c:770
#6  0xXXXXXXXXXXXXXXXX in FatalError (f=f@entry=0x5c6648 "Caught signal %d (%s). Server aborting\n") at log.c:911
#7  0xXXXXXXXXXXXXXXXX in OsSigHandler (signo=11, sip=<optimized out>, unused=<optimized out>) at osinit.c:147
#8  <signal handler called>