Version: 2.10

What were you doing when the application crashed?
Closing evolution.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:21:43 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 608550912 vsize: 608550912 resident: 61177856 share: 28184576 rss: 61177856 rss_rlim: 18446744073709551615
CPU usage: start_time: 1186844439 rtime: 429 utime: 358 stime: 71 cutime:357 cstime: 51 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496521360 (LWP 9643)]
[New Thread 1147169104 (LWP 10241)]
[New Thread 1115965776 (LWP 9737)]
[New Thread 1115699536 (LWP 9736)]
(no debugging symbols found)
0x000000346760d97f in waitpid () from /lib64/libpthread.so.0

+ Trace 154433

----------- .xsession-errors (30 sec old) ---------------------
(evolution:9643): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:9643): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:9643): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:9643): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:9643): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:9643): camel-WARNING **: camel_exception_get_id called with NULL parameter.
(evolution:9643): camel-WARNING **: camel_exception_get_id called with NULL parameter.
report junk?? R:O:L:E:X now on SALE , C:A:R:T:I:E:R , Breitling SAVE!! i
--------------------------------------------------