On Sun, Nov 27, 2011 at 4:28 AM, Carsten Haitzler ras...@rasterman.com wrote:
On Sun, 27 Nov 2011 00:06:44 +0100 Andreas Volz li...@brachttal.net said:
Am Sat, 26 Nov 2011 20:38:35 +0900 schrieb Carsten Haitzler (The
Rasterman):
Hm, would you vote for an EFL library bug or for a bug in my
Am Sat, 26 Nov 2011 13:21:11 +0900 schrieb Carsten Haitzler (The
Rasterman):
I don't think that I've activated threadsafety in ecore. If I run
configure again in ecore I get:
Ecore: always
Thread support.: POSIX
Thread safety..: no
So I
On Sat, 26 Nov 2011 11:00:55 +0100 Andreas Volz li...@brachttal.net said:
oh yes you're right - its just the ecore thread correctness detection code.
somethng is not doing lock/unlock correctly on enter/exit of ecore funcs... we
just dont know what.
Am Sat, 26 Nov 2011 13:21:11 +0900 schrieb
Am Sat, 26 Nov 2011 20:38:35 +0900 schrieb Carsten Haitzler (The
Rasterman):
Hm, would you vote for an EFL library bug or for a bug in my
application?
I have a multi-threading application. But I'm using pthreads and sure
not to call ecore lock/unlock directly, but the pthread locking
functions.
On Sun, 27 Nov 2011 00:06:44 +0100 Andreas Volz li...@brachttal.net said:
Am Sat, 26 Nov 2011 20:38:35 +0900 schrieb Carsten Haitzler (The
Rasterman):
Hm, would you vote for an EFL library bug or for a bug in my
application?
I have a multi-threading application. But I'm using pthreads
Hello,
in rare cases I get this assert in my application:
lt-oiui: ecore_private.h:248: _ecore_unlock: Zusicherung
»_ecore_main_lock_count == 0« nicht erfüllt.
lt-oiui: ecore_private.h:241: _ecore_lock: Zusicherung »_ecore_main_lock_count
== 1« nicht erfüllt.
This is gdb backtrace:
Program
On Fri, 25 Nov 2011 23:28:54 +0100 Andreas Volz li...@brachttal.net said:
well this is a bug in the threadsafety locks in ecore - they really haven't
been tested much or used, so best is not to enable them. they are disabled by
default.
Hello,
in rare cases I get this assert in my
