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 668804 - Crash in ecbm_connect_user()
Crash in ecbm_connect_user()
Status: RESOLVED FIXED
Product: evolution-mapi
Classification: Applications
Component: Calendar
3.3.x
Other Linux
: Normal critical
: ---
Assigned To: evolution-mapi-maint
evolution-mapi-maint
Depends on:
Blocks:
 
 
Reported: 2012-01-27 06:42 UTC by Akhil Laddha
Modified: 2012-02-01 13:37 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
ema patch (8.77 KB, patch)
2012-02-01 13:36 UTC, Milan Crha 		committed Details | Review

Description Akhil Laddha 2012-01-27 06:42:48 UTC 
Evolution 3.3.5

don't remember any specific operation, playing around Notes, later tried to quit evolution and in the middle evolution-calendar-factory crashed.

Program received signal SIGSEGV, Segmentation fault.

+ Trace 229528

Thread 2 (Thread 0xb6781b70 (LWP 12638))

  • #0 read
    at ../sysdeps/unix/syscall-template.S line 82
  • #1 read
    at /usr/include/bits/unistd.h line 45
  • #2 unix_signal_helper_thread
    at gmain.c line 4551
  • #3 g_thread_create_proxy
    at gthread.c line 1962
  • #4 start_thread
    at pthread_create.c line 301
  • #5 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 133 






Comment 1


Milan Crha





          2012-02-01 09:06:30 UTC
        



Confirming, I just got similar crash:





+
Trace
    229573






Thread 7
          (Thread 0x7f5cd27fc700 (LWP 1887))


    

  • 
#0
waitpid

    
                from
                /lib64/libpthread.so.0

    

    • 

  • 
#1
g_spawn_sync

    
                at gspawn.c
                  line
                  404

    

    • 

  • 
#2
g_spawn_command_line_sync

    
                at gspawn.c
                  line
                  717

    

    • 

  • 
#3
run_bug_buddy

    
                at gnome-segvhanlder.c
                  line
                  240

    

    • 

  • 
#4
bugbuddy_segv_handle

    
                at gnome-segvhanlder.c
                  line
                  191

    

    • 

  • 
#5
<signal handler called>

    • 

  • 
#6
ecbm_connect_user

    
                at e-cal-backend-mapi.c
                  line
                  1156

    

    • 

  • 
#7
ecbm_authenticate_user

    
                at e-cal-backend-mapi.c
                  line
                  1317

    

    • 

  • 
#8
ecbm_operation_cb

    
                at e-cal-backend-mapi.c
                  line
                  2599

    

    • 

  • 
#9
thread_func_cb

    
                at e-mapi-operation-queue.c
                  line
                  144

    

    • 

  • 
#10
g_thread_pool_thread_proxy

    
                at gthreadpool.c
                  line
                  319

    

    • 

  • 
#11
g_thread_create_proxy

    
                at gthread.c
                  line
                  1962

    

    • 

  • 
#12
start_thread

    
                from
                /lib64/libpthread.so.0

    

    • 

  • 
#13
clone

    
                from
                /lib64/libc.so.6

    

    • 













Comment 2


Milan Crha





          2012-02-01 13:36:12 UTC
        



Created attachment 206570 [details] [review]
ema patch

for evolution-mapi;

OK, so the backend could be freed while other parts of ema were using it (even indirectly). Thus it needs a little bit of reffing. It's done similarly in addressbook backend.






Comment 3


Milan Crha





          2012-02-01 13:37:09 UTC
        



Created commit ef578a6 in ema master (3.3.5+)