On Mon, 13 Jun 2011 17:06:20 +0200 (CEST) Vincent Torri
said:
>
>
> On Mon, 13 Jun 2011, Carsten Haitzler (The Rasterman) wrote:
>
> > On Thu, 2 Jun 2011 09:52:02 +0200 (CEST) Vincent Torri
> > said:
> >
> > well the comments and printfs say whats going on. LKT is try get lock. if it
> > stay
On Mon, 13 Jun 2011, Carsten Haitzler (The Rasterman) wrote:
> On Thu, 2 Jun 2011 09:52:02 +0200 (CEST) Vincent Torri
> said:
>
> well the comments and printfs say whats going on. LKT is try get lock. if it
> stays locked for too long it decides there is a deadlock. why is ret ALWAYS
> fails. t
On Thu, 2 Jun 2011 09:52:02 +0200 (CEST) Vincent Torri
said:
well the comments and printfs say whats going on. LKT is try get lock. if it
stays locked for too long it decides there is a deadlock. why is ret ALWAYS
fails. that means something is locking it almost ALWAYS.without unlocking it,
so so
On Thu, 2 Jun 2011, Vincent Torri wrote:
>
> hey,
>
> currently, on Windows, i build evas without async preload (expedite
> segfault in evas_object_text, i don't know why at all).
expedite segfault if i build evas *with* async preload. it works without
but there are the messages...
Vincent
-
hey,
currently, on Windows, i build evas without async preload (expedite
segfault in evas_object_text, i don't know why at all).
The problem of building evas without async preload is that there is a
plethora of messages that are sidplayed in the terminal. The reason is:
1) in evas_common.h, L
