Bug 787465

Summary: [abrt] evolution-3.2.3-1.fc16: __GI_raise: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Daniel <daniel.distler>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: lucilanga, mbarnes, mcrha
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:37f0b2ab0b8b01272d0fa47c3179a067fcae93d1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-06 12:15:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: dso_list
none
File: build_ids
none
File: maps
none
File: backtrace none

Description Daniel 2012-02-05 10:08:55 UTC 
libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 4
cmdline:        evolution
comment:        crash after reconnecting from offline mode
crash_function: __GI_raise
executable:     /usr/bin/evolution
kernel:         3.2.2-1.fc16.x86_64
pid:            2115
reason:         Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
time:           Sat 04 Feb 2012 08:05:59 PM CET
uid:            1000

backtrace:      Text file, 78128 bytes
build_ids:      Text file, 7585 bytes
dso_list:       Text file, 19113 bytes
maps:           Text file, 87735 bytes

environ:
:XDG_VTNR=1
:XDG_SESSION_ID=2
:HOSTNAME=<hostname>
:IMSETTINGS_INTEGRATE_DESKTOP=yes
:SHELL=/bin/bash
:TERM=dumb
:HISTSIZE=1000
:XDG_SESSION_COOKIE=eca7cccfcd41b2033e609e910000001c-1328270731.258190-1372858698
:GNOME_KEYRING_CONTROL=/tmp/keyring-8j1IRl
:IMSETTINGS_MODULE=none
:USER=<user>
:USERNAME=<user>
:MAIL=/var/spool/mail/<user>
:PATH=/home/<user>/local/scripts:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/<user>/bin
:DESKTOP_SESSION=gnome
:QT_IM_MODULE=xim
:PWD=/home/<user>
:XMODIFIERS=@im=none
:EDITOR=emacs
:GNOME_KEYRING_PID=1528
:LANG=en_US.utf8
:GDM_LANG=en_US.utf8
:GDMSESSION=gnome
:HISTCONTROL=ignoredups
:HOME=/home/<user>
:XDG_SEAT=seat0
:SHLVL=1
:LOGNAME=<user>
:DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-D0tZT0VKYB,guid=85de21f73f88a6cb995f9c520000002e
:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
:WINDOWPATH=1
:XDG_RUNTIME_DIR=/run/user/<user>
:DISPLAY=:0
:XAUTHORITY=/var/run/gdm/auth-for-<user>-gJUCY4/database
:_=/usr/bin/gnome-session
:GNOME_DESKTOP_SESSION_ID=this-is-deprecated
:SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/1533,unix/unix:/tmp/.ICE-unix/1533
:GPG_AGENT_INFO=/tmp/keyring-8j1IRl/gpg:0:1
:SSH_AUTH_SOCK=/tmp/keyring-8j1IRl/ssh
:GJS_DEBUG_OUTPUT=stderr
:'GJS_DEBUG_TOPICS=JS ERROR;JS LOG'
:DESKTOP_STARTUP_ID=gnome-shell-1791-<hostname>-evolution-0_TIME94113
:GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/evolution.desktop
:GIO_LAUNCHED_DESKTOP_FILE_PID=2115
Comment 1 Daniel 2012-02-05 10:08:59 UTC 
Created attachment 559454 [details]
File: dso_list
Comment 2 Daniel 2012-02-05 10:09:01 UTC 
Created attachment 559455 [details]
File: build_ids
Comment 3 Daniel 2012-02-05 10:09:04 UTC 
Created attachment 559456 [details]
File: maps
Comment 4 Daniel 2012-02-05 10:09:07 UTC 
Created attachment 559457 [details]
File: backtrace
Comment 5 Milan Crha 2012-02-06 10:45:46 UTC 
Thanks for a bug report. There had been reported a similar bug report already, thus I'm marking it as a duplicate.

*** This bug has been marked as a duplicate of bug 773691 ***
Comment 6 Daniel 2012-02-06 11:06:58 UTC 
thanks for your prompt feedback, but I don't see the similarity.
While the function imapx_job_scan_changes_done from bug 773691 is somewhere in my back trace, it is in the BT of thread 2, while the call to __GI_raise is in thread 1. The signal in bug 773691 is SIGSEGV, while here it is SIGABRT.

different threads + different signals => different bug?
Comment 7 Milan Crha 2012-02-06 12:15:46 UTC 
(In reply to comment #6)
> different threads + different signals => different bug?

Yes and no. In other words: it depends. Thread numbering is kinda different with ABRT, as Thread 1 doesn't mean thread where the main loop is run, but thread where the crash had been catch.

If you look carefully, then Thread 2 is in
>  malloc_printerr (action=3, str=0x3e2cf71b4c "corrupted double-linked list",
> ptr=<optimized out>)
which means there is something wrong in memory. Thread 1 recognized it too, and decided to abort, sooner than Thread 2.
Thread 2 is in imapx_job_scan_changes_done().

Bug #773691 is about memory corruption being recognized around the same function, imapx_job_scan_changes_done(). As memory corruption likes to do, it can cause a crash sooner or later, and in your case it's rather later.

The above is a reason why I believe these two are same issue.

*** This bug has been marked as a duplicate of bug 773691 ***
Comment 8 Daniel 2012-02-06 13:49:42 UTC 
You are right. I should have looked more thoroughly.
Thanks for the feedback and sorry for the noise!