Bug 354152 – Crash for no clear reason

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 354152 - Crash for no clear reason


Summary:	Crash for no clear reason


Status:	RESOLVED OBSOLETE

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	2.8.x (obsolete)
Hardware:	Other Linux

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-mail-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-09-03 17:34 UTC by Reinout van Schouwen
Modified:	2009-05-28 08:59 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description Reinout van Schouwen 2006-09-03 17:34:20 UTC

I was simply reading some messages when this crash happened:

Memory status: size: 211996672 vsize: 0 resident: 211996672 share: 0 rss: 83767296 rss_rlim: 0
CPU usage: start_time: 1157280172 rtime: 0 utime: 2682 stime: 0 cutime:2288 cstime: 0 timeout: 394 it_real_value: 0 frequency: 960

Backtrace was generated from '/usr/bin/evolution-2.8'

Using host libthread_db library "/lib/i686/libthread_db.so.1".
`shared object read from target memory' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1236064032 (LWP 10029)]
[New Thread -1310815328 (LWP 11491)]
[New Thread -1302422624 (LWP 11441)]
[New Thread -1242883168 (LWP 11419)]
[New Thread -1287558240 (LWP 10065)]
[New Thread -1269273696 (LWP 10063)]
[New Thread -1260880992 (LWP 10062)]
[New Thread -1251275872 (LWP 10061)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 71504

Thread 8 (Thread -1251275872 (LWP 10061))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/i686/libpthread.so.0
#2 libgnomeui_segv_handle
at gnome-ui-init.c line 867

Comment 1 André Klapper 2006-09-04 06:22:17 UTC

Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. :-/

Comment 2 Reinout van Schouwen 2006-09-04 07:03:40 UTC

Err.. this trace *does* contain debugging symbols.

Comment 3 André Klapper 2006-09-04 10:19:44 UTC

argh... right. sorry.

Comment 4 Matthew Barnes 2008-03-11 00:26:40 UTC

Bumping version to a stable release.

Comment 5 Paul Bolle 2008-12-17 21:11:58 UTC

This trace does contain debugging symbols but the traces of each thread looks truncated to me. Since two years have passed this now is also about a rather old version of evolution. Is there anything that still can be done here?

Comment 6 Akhil Laddha 2009-05-28 07:40:43 UTC

Could you please confirm if this bug is still happening at your end ? Please try in 2.24.x / 2.26.x and report back, thanks.

Comment 7 Reinout van Schouwen 2009-05-28 08:59:23 UTC

No, it's not happening any more.