Hello. I have encountered a possible bug in ecore 1.7.5
I have an ARM platform that runs (yet) a simple app with a text clock. Rarely it crashes with a coredump. I got following stack trace: #0 _ecore_fb_li_device_fd_callback (data=<value optimized out>, fdh=<value optimized out>) at ecore_fb_li.c:412 #1 0xb6bef228 in _ecore_main_loop_iterate_internal (once_only=0) at ecore_private.h:345 #2 0xb6bef3e0 in ecore_main_loop_begin () at ecore_main.c:956 #3 0x00009448 in elm_main (argc=1, argv=0xbe995e74) at ../hello.c:163 #4 0x000094f8 in main (argc=1, argv=0xbe995e74) at ../hello.c:171 (gdb) print i $18 = 119 code is dev = (Ecore_Fb_Input_Device*)data; /* read up to 64 events at once */ len = read(dev->fd, &ev, sizeof(ev)); for(i = 0; i < (int)(len / sizeof(ev[0])); i++) { switch(ev[i].type) <-- i equals 119 == segfault { I assume somehow read function returned more than 1k. I can provide additional info from coredump upon needs. It is possible that it's a bug in libc/toolchain. I use glibc 2.10.2, gcc 4.4.3, it's not easy to change toolchain in my project, but I hope it's sort of an internal EFL problem. Thanks. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel