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 508033 - crash in Evolution: Evo was left running ove...
crash in Evolution: Evo was left running ove...
Status: RESOLVED DUPLICATE of bug 489501
Product: evolution
Classification: Applications
Component: general
2.12.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-01-08 12:13 UTC by Reid Thompson
Modified: 2008-01-31 22:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Reid Thompson 2008-01-08 12:13:04 UTC
What were you doing when the application crashed?
Evo was left running overnight -- came in to a crash


Distribution: Gentoo Base System release 1.12.10
Gnome Release: 2.20.2 2007-11-29 (Gentoo)
BugBuddy Version: 2.20.1

System: Linux 2.6.23-gentoo-r3 #2 SMP PREEMPT Wed Dec 5 11:15:01 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: marble-look
Icon Theme: gnome

Memory status: size: 85217280 vsize: 85217280 resident: 28692480 share: 9801728 rss: 28692480 rss_rlim: 4294967295
CPU usage: start_time: 1199742048 rtime: 290 utime: 255 stime: 35 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/evolution-exchange-storage'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb63736c0 (LWP 20932)]
[New Thread 0xb60cbb90 (LWP 20934)]
0xb7f14410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb63736c0 (LWP 20932))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 369
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 677
  • #4 run_bug_buddy
    at gnome-breakpad.cc line 213
  • #5 check_if_gdb
    at gnome-breakpad.cc line 283
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 225
  • #7 google_breakpad::ExceptionHandler::HandleException
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 196
  • #8 <signal handler called>
  • #9 strchr
    from /lib/libc.so.6
  • #10 soup_uri_new_with_base
    at soup-uri.c line 68
  • #11 soup_uri_new
    at soup-uri.c line 247
  • #12 soup_message_new
    at soup-message.c line 293
  • #13 e2k_soup_message_new
    at e2k-context.c line 796
  • #14 e2k_soup_message_new_full
    at e2k-context.c line 827
  • #15 patch_msg
    at e2k-context.c line 1422
  • #16 e2k_context_proppatch
    at e2k-context.c line 1462
  • #17 set_replied_flags
    at mail-stub-exchange.c line 1730
  • #18 process_flags
    at mail-stub-exchange.c line 1854
  • #19 g_timeout_dispatch
    at gmain.c line 3488
  • #20 IA__g_main_context_dispatch
    at gmain.c line 2061
  • #21 g_main_context_iterate
    at gmain.c line 2694
  • #22 IA__g_main_loop_run
    at gmain.c line 2898
  • #23 bonobo_main
    at bonobo-main.c line 311
  • #24 main
    at main.c line 238
  • #0 __kernel_vsyscall


----------- .xsession-errors (14895 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 André Klapper 2008-01-31 22:53:56 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 489501 ***