[Bug 701604] [abrt] evolution-3.0.1-1.fc15: magazine_chain_pop_head: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)

bugzilla at redhat.com bugzilla at redhat.com
Wed Jun 22 06:03:59 UTC 2011


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=701604

Milan Crha <mcrha at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
               Flag|needinfo?                   |needinfo?(litcanu at gmail.com
                   |                            |)

--- Comment #19 from Milan Crha <mcrha at redhat.com> 2011-06-22 02:03:58 EDT ---
OK, so 3.0.2-2 exhibits the issue too. Does the common part of the crasher
involve evolution-rss for all reporters? I see that it does for most of you.
Valgrind may help us to see what happens to the memory. If anyone of you can
try similar steps on your machine, when having run evolution like shown below,
then it'll be great. Before running it, please make sure you've installed
correct debug info packages (same version as binary packages) for gtkhtml3, 
evolution-data-server, evolution and evolution-rss, then run evolution like
this:
   $ G_SLICE=always-malloc valgrind --num-callers=50 evolution &>log.txt
and then repeat steps you did previously. Valgrind can avoid certain types of
crashes, thus it's possible it will not crash, but it may report a memory issue
into the resulting log.txt file. Please attach the file here, for an
examination. Thanks in advance.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


More information about the fonts-bugs mailing list