[Evolution-hackers] g_mutex, e_mutex and pthread_mutex in camel?!

Is there a reason why g_mutex, e_mutex and pthread_mutex are used in a
mixed may on libcamel?

Anyway, I'm getting this segmentation fault on the
CAMEL_DATA_WRAPPER_UNLOCK call in camel-data-wrapper.c 

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1226287424 (LWP 16199)]
0x00001098 in ?? ()
(gdb) bt
#0  0x00001098 in ?? ()
#1  0x00000012 in ?? ()
#2  0x00000f40 in ?? ()
#3  0xb7a3d653 in write_to_stream (data_wrapper=0x8067aa8,
stream=0x8067c58) at camel-data-wrapper.c:149
#4  0xb7a3d6d7 in camel_data_wrapper_write_to_stream
(data_wrapper=0x8067aa8, stream=0x8067a38) at camel-data-wrapper.c:175

Philip Van Hoof, software developer at x-tend 
home: me at pvanhoof dot be 
gnome: pvanhoof at gnome dot org 
work: vanhoof at x-tend dot be 
http://www.pvanhoof.be - http://www.x-tend.be

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]