that is entirely bizarre. what backtraces do you get?
I do not know precisely what you need: is there some kind of tracing
facility beside setting the info.debug flag via the evas_engine_info_set()
call that I missed?
Anyway, compiling test.c[1], I just get this segfault output[2].
Running it through valgrind's memcheck tool, I get this[3]. Line 329
of my evas installment (around evas 0.9.9.007, taken from CVS) read:
obj2 = evas_object_below_get_internal(obj2);
When removing the call to evas_object_bottom_get(), I hit the very same
error on the corresponding call of evas_object_above_internal()...
Of course, that's just an expurged version: I get similar errors every
time I try using those two calls in a more complete code when the rest
of Evas works fine...
--
S.Fourmanoit <[EMAIL PROTECTED]>
With your bare hands?!?
[1] http://adesklets.sf.net/verbatim/test.c
[2] http://adesklets.sf.net/verbatim/test.out
[3] http://adesklets.sf.net/verbatim/test.log
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
