evolution-2.28.3-24.el6: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)

Latest response

I am getting this a lot once I setup evolution to access our exchange 2010 environment. any ideas?

 

 

As a primary analysis of the coredump You are getting a segfault in bonobo server in evolution
segmentation fault can occur under the following circumstances:
 
1. A bug (software defect) in the program or command is encountered, for example a buffer overflow (an attempt to access memory beyond the end of an array).This can typically can be resolved by applying errata or vendor software updates.
2. A hardware problem affects the virtual memory subsystem. For example, a RAM DIMM or CPU cache is defective.
3. An attempt is made to execute a program that was not compiled/built correctly.
 
From the given coredump we got the following backtrace
==================================================
#23 0x000000362303cd55 in IA__g_main_loop_run (loop=0x109f300) at gmain.c:2799
#24 0x000000363582d0f6 in bonobo_main () at bonobo-main.c:311
#25 0x00000000004156aa in main (argc=<value optimized out>, argv=<value optimized out>) at main.c:732
(gdb) q
===================================================
 
 
(gdb) list
306
307 loop = g_main_loop_new (NULL, TRUE);
308 bonobo_main_loops = g_slist_prepend (bonobo_main_loops, loop);
309
310 if (g_main_loop_is_running (bonobo_main_loops->data))
311 g_main_loop_run (loop);
312
313 bonobo_main_loops = g_slist_remove (bonobo_main_loops, loop);
314
315 g_main_loop_unref (loop);
(gdb) 
 
Here it activating the Bonobo POA Manager and enters the main event loop. 
 
I have checked but i didnt get any already reported bugzilla  on this issue.
ya
Log in to join the conversation

Responses

David Powles's picture Red Hat 25369 points
14 January 2013 7:24 AM

Hi Richard,

No takers from the community on this one so far, it seems. I've reached out to a few folks here so I'll see if we can get you some help soon.

rh Red Hat Guru 4540 points
14 January 2013 2:10 PM

Frankly I don't think community forums are the way to go to get a core dump analysed. What I would recommend instead is to please create a support case for this, with a sosreport and an application core dump as supporting information.

Refer to What is an sosreport and how do I create one in Red Hat Enterprise Linux 4.6 and later? and How do I enable core file dumps when my application crashes or segmentation faults? for details.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.