Hi Raster,

On Tue, 16 April 2013 Carsten Haitzler wrote:
> On Mon, 15 Apr 2013 23:08:41 +0200 Bruno said:
> could you give more details - like it crashes immediately on start?

Yes, the crash happens during early startup of enlightenment, right after
painting background and setting up cursor.

> you are is the depth 16bpp BUT the visual is still 24bpp with 24bpp rgb
> masks? xdpyinfo will tell you this. i.e.

According to xdpyinfo, with driver prior to bisected commit root window
is 24bit but with 2.21.6 it is 15bit.

Also of interest, with 2.21.6 there are much fewer visuals listed: 15bit
default, 15bit and 32bit while last working one show lots of 24bit visuals.
Maybe the difference in number comes from the moment when xdpyinfo is called.
For 2.21.6 right after starting Xorg, as only X client.
For last good commit from xterm while running under enlightenment.

See attached xpdyinfo outputs attached to the bug report.
  https://bugs.freedesktop.org/show_bug.cgi?id=63572

> more information needed. also consider using valgrind to catch the problem
> earlier.

A valgrind trace is not very informative. It reports a bad write and later
a segfault quite a few bytes after the address of bad write.

==5361== Invalid write of size 4
==5361==    at 0x40FFE90: evas_common_scale_rgba_in_to_out_clip_smooth_mmx 
(evas_scale_smooth_scaler_downx_downy.c:239)
==5361==    by 0x4102D6C: evas_common_scale_rgba_in_to_out_clip_smooth 
(evas_scale_smooth.c:513)
==5361==    by 0x40F9314: evas_common_rgba_image_scalecache_do 
(evas_image_scalecache.c:796)
==5361==    by 0x4110153: eng_image_draw (evas_engine.c:915)
==5361==    by 0x4077A6B: evas_object_image_render (evas_object_image.c:3042)
==5361==    by 0x40BF34D: evas_render_mapped (evas_render.c:1160)
==5361==    by 0x40C1ABE: evas_render_updates_internal (evas_render.c:1575)
==5361==    by 0x41EBC83: _ecore_evas_x_render (ecore_evas_x.c:288)
==5361==    by 0x41E81AD: _ecore_evas_idle_enter (ecore_evas.c:59)
==5361==    by 0x4173D11: _ecore_idle_enterer_call (ecore_private.h:281)
==5361==    by 0x41758F4: _ecore_main_loop_iterate_internal (ecore_main.c:1833)
==5361==    by 0x4175DAE: ecore_main_loop_begin (ecore_main.c:956)
==5361==  Address 0x7f9c000 is not stack'd, malloc'd or (recently) free'd
==5361== 
==5361== 
==5361== Process terminating with default action of signal 11 (SIGSEGV)
==5361==  Access not within mapped region at address 0x7F9D770
==5361==    at 0x40FFE90: evas_common_scale_rgba_in_to_out_clip_smooth_mmx 
(evas_scale_smooth_scaler_downx_downy.c:239)
==5361==    by 0x4102D6C: evas_common_scale_rgba_in_to_out_clip_smooth 
(evas_scale_smooth.c:513)
==5361==    by 0x40F9314: evas_common_rgba_image_scalecache_do 
(evas_image_scalecache.c:796)
==5361==    by 0x4110153: eng_image_draw (evas_engine.c:915)
==5361==    by 0x4077A6B: evas_object_image_render (evas_object_image.c:3042)
==5361==    by 0x40BF34D: evas_render_mapped (evas_render.c:1160)
==5361==    by 0x40C1ABE: evas_render_updates_internal (evas_render.c:1575)
==5361==    by 0x41EBC83: _ecore_evas_x_render (ecore_evas_x.c:288)
==5361==    by 0x41E81AD: _ecore_evas_idle_enter (ecore_evas.c:59)
==5361==    by 0x4173D11: _ecore_idle_enterer_call (ecore_private.h:281)
==5361==    by 0x41758F4: _ecore_main_loop_iterate_internal (ecore_main.c:1833)
==5361==    by 0x4175DAE: ecore_main_loop_begin (ecore_main.c:956)
==5361==  If you believe this happened as a result of a stack
==5361==  overflow in your program's main thread (unlikely but
==5361==  possible), you can try to increase the size of the
==5361==  main thread stack using the --main-stacksize= flag.
==5361==  The main thread stack size used in this run was 8388608.
==5361== 

Full valgrind log attached to the bug.

Bruno

> > Since intel driver xf86-video-intel-2.21.4 evas crashes, preventing
> > enlightenment to start on my laptop.
> > 
> > I bisected it to a change in intel driver:
> >   a19da0ea517127052ae49cdd6441e8b6077ca523
> >   sna: Reduce DefaultDepth to 16 on older chipsets
> > 
> > Is the crash caused by wrong assumption on EFL/Enlightenment side?
> > 
> > See freedesktop bug report
> >    https://bugs.freedesktop.org/show_bug.cgi?id=63572
> > for enlightenment backtrace and 
> >    
> > http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=a19da0ea517127052ae49cdd6441e8b6077ca523
> > for the triggering commit.

------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to