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 601802 - segfault in message_info_to_db
segfault in message_info_to_db
Status: RESOLVED DUPLICATE of bug 574940
Product: evolution
Classification: Applications
Component: Mailer
2.28.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-11-13 13:20 UTC by Brian J. Murrell
Modified: 2009-11-13 16:32 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Brian J. Murrell 2009-11-13 13:20:34 UTC


Thread 1 (Thread 20237)

  • #0 message_info_to_db
    at camel-folder-summary.c line 3411
  • #1 save_to_db_cb
    at camel-folder-summary.c line 1475
  • #2 IA__g_hash_table_foreach
    at /build/buildd/glib2.0-2.22.2/glib/ghash.c line 1211
  • #3 save_message_infos_to_db
    at camel-folder-summary.c line 1532
  • #4 camel_folder_summary_save_to_db
    at camel-folder-summary.c line 1576
  • #5 filter_free
    at camel-folder.c line 2015
  • #6 session_thread_msg_free
    at camel-session.c line 576
  • #7 ms_thread_msg_free
    at mail-session.c line 613
  • #8 camel_session_thread_msg_free
    at camel-session.c line 689
  • #9 session_thread_proxy
    at camel-session.c line 596
  • #10 g_thread_pool_thread_proxy
    at /build/buildd/glib2.0-2.22.2/glib/gthreadpool.c line 265
  • #11 g_thread_create_proxy
    at /build/buildd/glib2.0-2.22.2/glib/gthread.c line 635
  • #12 start_thread
    at pthread_create.c line 300
  • #13 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 130

Comment 1 Fabio Durán Verdugo 2009-11-13 16:32:26 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 bug 574940 ***