Bug 546184 – disk-summary crash on search for labels

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 546184 - disk-summary crash on search for labels


Summary:	disk-summary crash on search for labels


Status:	RESOLVED FIXED

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	2.24.x (obsolete)
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	evolution-mail-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:	evolution[disk-summary]

Depends on:
Blocks:	543389

Reported:	2008-08-04 08:13 UTC by Milan Crha
Modified:	2013-09-13 00:58 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Milan Crha 2008-08-04 08:13:28 UTC

Just run today's evo and it crashed. See Thread 2:

[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0x7f4320d4b7f0 (LWP 6533)]
[New Thread 0x43269950 (LWP 6609)]
[New Thread 0x42868950 (LWP 6599)]
[New Thread 0x4506c950 (LWP 6597)]
[New Thread 0x41e67950 (LWP 6596)]
[New Thread 0x4466b950 (LWP 6583)]
0x00000039a8c0e86f in __libc_waitpid (pid=<value optimized out>, stat_loc=<value optimized out>, options=<value optimized out>)
    at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);

+ Trace 204530

Thread 2 (Thread 0x43269950 (LWP 6609))

#0 __lll_lock_wait
from /lib64/libpthread.so.0
#1 _L_lock_100
from /lib64/libpthread.so.0
#2 __pthread_mutex_lock
at pthread_mutex_lock.c line 86
#3 segv_redirect
at main.c line 517
#4 <signal handler called>
#5 camel_message_info_user_tag
at camel-folder-summary.c line 4374
#6 search_user_tag
at camel-folder-search.c line 1296
#7 e_sexp_term_eval
at e-sexp.c line 718
#8 term_eval_eq
at e-sexp.c line 448
#9 e_sexp_term_eval
at e-sexp.c line 708
#10 term_eval_or
at e-sexp.c line 320
#11 e_sexp_term_eval
at e-sexp.c line 708
#12 search_match_all
at camel-folder-search.c line 662
#13 e_sexp_term_eval
at e-sexp.c line 708
#14 term_eval_or
at e-sexp.c line 320
#15 e_sexp_term_eval
at e-sexp.c line 708
#16 e_sexp_eval
at e-sexp.c line 1320
#17 camel_folder_search_execute_expression
#18 search_by_uids
#19 camel_folder_search_by_uids
#20 folder_changed_change
at camel-vee-folder.c line 1353
#21 session_thread_proxy
at camel-session.c line 592
#22 g_thread_pool_thread_proxy
at gthreadpool.c line 265
#23 g_thread_create_proxy
at gthread.c line 635
#24 start_thread
at pthread_create.c line 297

Comment 1 Srinivasa Ragavan 2008-08-04 08:36:09 UTC

Exchange!!!

No idea, why Exchange uses camel_folder_search_execute_expression when rest of the world uses *search_search

Comment 2 Milan Crha 2008-08-04 14:28:38 UTC

me neither, who will solve?

Comment 3 Srinivasa Ragavan 2008-08-05 05:02:47 UTC

I will solve.. It is  a mix of exchange + vfolder issue. I will commit the fix today.

Comment 4 Srinivasa Ragavan 2008-08-05 05:24:12 UTC

Fixed in trunk.