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 556122 - Coredump on start, 2.25 svn
Coredump on start, 2.25 svn
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Mailer
2.24.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[disk-summary]
Depends on:
Blocks: 543389
 
 
Reported: 2008-10-13 12:09 UTC by C de-Avillez
Modified: 2009-01-15 16:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description C de-Avillez 2008-10-13 12:09:35 UTC 
just starting it up, got core.

Program terminated with signal 11, Segmentation fault.
[New process 16131]
[New process 16039]
[New process 16069]
[New process 16060]
[New process 16133]
[New process 16038]
[New process 16036]
[New process 16132]
[New process 15995]

+ Trace 208097

  • #0 malloc_consolidate
    from /lib/libc.so.6
  • #0 malloc_consolidate
    from /lib/libc.so.6
  • #1 _int_malloc
    from /lib/libc.so.6
  • #2 malloc
    from /lib/libc.so.6
  • #3 sqlite3_malloc
    at sqlite3.c line 11101
  • #4 pagerAcquire
    at sqlite3.c line 27312
  • #5 sqlite3BtreeGetPage
    at sqlite3.c line 27520
  • #6 allocateBtreePage
    at sqlite3.c line 34112
  • #7 balance
    at sqlite3.c line 35463
  • #8 sqlite3BtreeInsert
    at sqlite3.c line 35667
  • #9 sqlite3VdbeExec
    at sqlite3.c line 45747
  • #10 sqlite3_step
    at sqlite3.c line 41212
  • #11 sqlite3_exec
    at sqlite3.c line 60363
  • #12 camel_db_select
    at ../../../evolution-data-server/camel/camel-db.c line 459
  • #13 camel_db_get_folder_uids
    at ../../../evolution-data-server/camel/camel-db.c line 585
  • #14 camel_folder_summary_load_from_db
    at ../../../evolution-data-server/camel/camel-folder-summary.c line 918
  • #15 camel_imap_summary_new
    at ../../../../../evolution-data-server/camel/providers/imap/camel-imap-summary.c line 192
  • #16 camel_imap_folder_new
    at ../../../../../evolution-data-server/camel/providers/imap/camel-imap-folder.c line 245
  • #17 get_folder_offline
    at ../../../../../evolution-data-server/camel/providers/imap/camel-imap-store.c line 2040
  • #18 get_folder
    at ../../../../../evolution-data-server/camel/providers/imap/camel-imap-store.c line 1806
  • #19 camel_store_get_folder
    at ../../../evolution-data-server/camel/camel-store.c line 327
  • #20 imap_can_refresh_folder
    at ../../../../../evolution-data-server/camel/providers/imap/camel-imap-store.c line 3079
  • #21 camel_store_can_refresh_folder
    at ../../../evolution-data-server/camel/camel-store.c line 1363
  • #22 get_folders
    at ../../../evolution/mail/mail-send-recv.c line 783
  • #23 get_folders
    at ../../../evolution/mail/mail-send-recv.c line 787
  • #24 get_folders
    at ../../../evolution/mail/mail-send-recv.c line 787
  • #25 refresh_folders_exec
    at ../../../evolution/mail/mail-send-recv.c line 814
  • #26 mail_msg_proxy
    at ../../../evolution/mail/mail-mt.c line 520
  • #27 g_thread_pool_thread_proxy
    at /build/buildd/glib2.0-2.18.1/glib/gthreadpool.c line 265
  • #28 g_thread_create_proxy
    at /build/buildd/glib2.0-2.18.1/glib/gthread.c line 635
  • #29 start_thread
    from /lib/libpthread.so.0
  • #30 clone
    from /lib/libc.so.6
  • #31 ?? 
(gdb)
Comment 1 Srinivasa Ragavan 2008-10-14 18:39:25 UTC 
Don't think its evo specific. Mostly to do with sqlite. Is it reproducible?
Comment 2 C de-Avillez 2008-10-14 22:32:11 UTC 
No, Srinivasa, unfortunately not at will.

I *do* get it every so often -- about once every few days, If I remember it correctly, it usually happens when I close & re-start Evo.
Comment 3 Srinivasa Ragavan 2008-11-18 04:28:45 UTC 
Some one, akhil or so told be this happens when he builds sqlite and not using the system sqlite. Akhil is that you?
Comment 4 Akhil Laddha 2008-11-18 04:44:02 UTC 
I got this info from #sqlite channel (irc.freenode.net)

http://www.mail-archive.com/sqlite-users@sqlite.org/msg35130.html

http://www.mail-archive.com/sqlite-users@sqlite.org/msg35139.html
Comment 5 Akhil Laddha 2009-01-15 05:42:15 UTC 
 hggdh , I guess we can close the bug ?
Comment 6 C de-Avillez 2009-01-15 16:45:33 UTC 
yes, guess so. Even more because I have not getting it anymore. So, whatever caused it is gone, and I probably will not be able to find it.

So, closing incomplete.