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 404897 - crash in Evolution: Selected a folder and cl...
crash in Evolution: Selected a folder and cl...
Status: RESOLVED DUPLICATE of bug 387646
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-02-06 09:26 UTC by vms
Modified: 2007-08-23 05:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description vms 2007-02-06 09:26:38 UTC
What were you doing when the application crashed?
Selected a folder and clicked remove.


Distribution: Gentoo Base System version 1.12.6
Gnome Release: 2.16.2 2006-12-11 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 168345600 vsize: 0 resident: 168345600 share: 0 rss: 28925952 rss_rlim: 0
CPU usage: start_time: 1170753869 rtime: 0 utime: 332 stime: 0 cutime:273 cstime: 0 timeout: 59 it_real_value: 0 frequency: 0

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1230768464 (LWP 27951)]
[New Thread -1349149792 (LWP 27985)]
[New Thread -1297110112 (LWP 27980)]
[New Thread -1288717408 (LWP 27979)]
[New Thread -1355859040 (LWP 27978)]
[New Thread -1364251744 (LWP 27974)]
[New Thread -1313895520 (LWP 27972)]
[New Thread -1339073632 (LWP 27969)]
[New Thread -1330680928 (LWP 27968)]
[New Thread -1280324704 (LWP 27962)]
[New Thread -1271932000 (LWP 27961)]
[New Thread -1263539296 (LWP 27960)]
[New Thread -1255146592 (LWP 27959)]
[New Thread -1245070432 (LWP 27958)]
0xffffe410 in __kernel_vsyscall ()

Comment 1 palfrey 2007-02-06 17:47:45 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 vms 2007-02-06 22:13:14 UTC
Hello,

I hope the below information is enough, if not please tell me.

---------------------------------------

camel-ERROR **: file camel-partition-table.c: line 829 (camel_key_table_set_flags): assertion failed: (kb->used < 127)
aborting...

Program received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread -1231243600 (LWP 9731)]
0xb6b932b1 in IA__g_logv (log_domain=0xb7d28754 "camel", 
    log_level=G_LOG_LEVEL_ERROR, 
    format=0xb6bbde20 "file %s: line %d (%s): assertion failed: (%s)", 
    args1=0xbfdcda3c "\n���=\003") at gmessages.c:493
493     gmessages.c: No such file or directory.
        in gmessages.c
(gdb) thread apply all bt

Thread 1 (Thread -1231243600 (LWP 9731))

  • #0 IA__g_logv
  • #1 IA__g_log
  • #2 IA__g_assert_warning
    at gmessages.c line 552
  • #3 camel_key_table_set_flags
    at camel-partition-table.c line 830
  • #4 text_index_delete_name
    at camel-text-index.c line 677
  • #5 camel_index_delete_name
    at camel-index.c line 213
  • #6 camel_mbox_summary_sync_mbox
    at camel-mbox-summary.c line 973
  • #7 mbox_summary_sync_full
    at camel-mbox-summary.c line 628
  • #8 mbox_summary_sync
    at camel-mbox-summary.c line 882
  • #9 camel_local_summary_sync
    at camel-local-summary.c line 297
  • #10 local_sync
    at camel-local-folder.c line 498
  • #11 camel_folder_sync
    at camel-folder.c line 273
  • #12 emfu_delete_rec
    at em-folder-utils.c line 407
  • #13 emfu_delete_response
    at em-folder-utils.c line 429
  • #14 IA__g_cclosure_marshal_VOID__INT
    at gmarshal.c line 216
  • #15 IA__g_closure_invoke
    at gclosure.c line 490
  • #16 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #17 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #18 IA__g_signal_emit
    at gsignal.c line 2243
  • #19 gtk_dialog_response
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 ??
    from /usr/lib/libgobject-2.0.so.0
  • #25 ??
    from /usr/lib/libgobject-2.0.so.0
  • #26 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 ??
  • #28 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77

Comment 3 palfrey 2007-02-06 22:45:31 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 387646 ***
Comment 4 Lucky Wankhede 2007-08-23 05:33:01 UTC
Looks traces similar to 348149.
camel-partition-table.c:

#if 1
        g_assert(kb->used < 127); /* this should be more accurate */
        g_assert(index < kb->used);
#else
        if (kb->used >=127 || index >= kb->used) {
                g_warning("Block %x: Invalid index or content: index %d used
%d\n", blockid, index, kb->used);
                return 0;
        }
#endif