Re: [E-devel] e17 segfault on fresh install
On 10/15/2011 04:20 AM, Jim Kukunas wrote: On Fri, Oct 14, 2011 at 03:18:48PM +1100, Jochen Schröder wrote: Hi all, I just rebuild all of EFL and E17 gives me a segfault when starting with a clean config directory. Seems to be related to the recent sse3 work. What is your compiler version and CFLAGS? Just realised my CFLAGS contained -msse4 (probably from when I copied the build script over from a different PC). I just recompiled without -msse4 and it is working now (cflags: -g3,-ggdb,-march=core2,-mfpmath=sse,-msse,-msse2,-msse3,-O2) Seams that that was the problem, sorry for the noise. Cheers Jochen The parameters to _mm_set_epi32 look reasonable. The only reason I could imagine this failing is if your compiler isn't aligning things properly. cat /proc/cpuinfo processor: 1 vendor_id: GenuineIntel cpu family : 6 model: 15 model name : Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz stepping : 11 cpu MHz : 1998.000 cache size : 4096 KB physical id : 0 siblings : 2 core id : 1 cpu cores: 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception: yes cpuid level : 10 wp : yes flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dts tpr_shadow vnmi flexpriority bogomips : 4654.98 clflush size : 64 cache_alignment : 64 address sizes: 36 bits physical, 48 bits virtual power management: bt attached. Cheers Jochen #0 0x7fa75897cbce in waitpid () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00435961 in e_alert_show (sig=optimized out) at e_alert.c:57 #2signal handler called #3 0x7fa75b037cc5 in _mm_set_epi32 (__q0=255, __q1=255, __q2=255, __q3=255) at /usr/lib/gcc/x86_64-linux-gnu/4.6/include/emmintrin.h:586 #4 _op_blend_mas_can_dp_sse3 (s=optimized out, m=0x1e7a4e1 \377\377\377\377\377\377, c=4278190080, d=0x7fa74c8b0df0, l=4) at op_blend_mask_color_sse3.c:79 #5 0x7fa75b01c147 in evas_common_font_draw_internal (dst=0x2268b70, dc=0x21c0eb0, x=29, y=12, text_props=0x21c4718, func=0x7fa75b037850_op_blend_mas_can_dp_sse3, ext_x=29, ext_y=2, ext_w=313, ext_h=15, im_w=377, fn=optimized out, im_h=optimized out) at evas_font_draw.c:298 #6 0x7fa75b01c4cb in evas_common_font_draw (dst=0x2268b70, dc=0x21c0eb0, fn=optimized out, x=29, y=12, text_props=0x21c4718) at evas_font_draw.c:418 #7 0x7fa74f3893ea in eng_font_draw (data=optimized out, context=optimized out, surface=optimized out, font=optimized out, x=optimized out, y=optimized out, w=313, h=15, ow=313, oh=15, text_props=0x21c4718) at evas_engine.c:898 #8 0x7fa75afd609f in evas_object_text_render (obj=0x214e480, output=0x21c1380, context=0x21c0eb0, surface=0x2268b70, x=0, y=0) at evas_object_text.c:1665 #9 0x7fa75afebd3e in evas_render_mapped (e=0x21c37a0, obj=0x214e480, context=0x21c0eb0, surface=0x2268b70, off_x=0, off_y=0, mapped=0, ecx=0, ecy=0, ecw=377, ech=22) at evas_render.c:1256 #10 0x7fa75afeeaf1 in evas_render_updates_internal (e=0x21c37a0, make_updates=1 '\001', do_draw=1 '\001') at evas_render.c:1579 #11 0x7fa75a911d65 in _ecore_evas_x_render (ee=0x21c3580) at ecore_evas_x.c:256 #12 0x7fa75a90f041 in _ecore_evas_idle_enter (data=optimized out) at ecore_evas.c:52 #13 0x7fa75ad6c1de in _ecore_call_task_cb (data=optimized out, func=optimized out) at ecore_private.h:246 #14 _ecore_idle_enterer_call () at ecore_idle_enterer.c:165 #15 0x7fa75ad6daf5 in _ecore_main_loop_iterate_internal (once_only=0) at ecore_main.c:1699 #16 0x7fa75ad6debf in ecore_main_loop_begin () at ecore_main.c:864 #17 0x00433bf7 in main (argc=optimized out, argv=optimized out) at e_main.c:954 quit A debugging session is active. Inferior 1 [process 2371] will be detached. Quit anyway? (y or n) Detaching from program: /opt/e17/bin/enlightenment, process 2371 -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- All the data continuously generated in your IT infrastructure contains a definitive record of
Re: [E-devel] e17 segfault on fresh install
On Mon, 17 Oct 2011 10:43:46 +1100 Jochen Schröder cycoma...@gmail.com said: On 10/15/2011 04:20 AM, Jim Kukunas wrote: On Fri, Oct 14, 2011 at 03:18:48PM +1100, Jochen Schröder wrote: Hi all, I just rebuild all of EFL and E17 gives me a segfault when starting with a clean config directory. Seems to be related to the recent sse3 work. What is your compiler version and CFLAGS? Just realised my CFLAGS contained -msse4 (probably from when I copied the build script over from a different PC). I just recompiled without -msse4 and it is working now (cflags: -g3,-ggdb,-march=core2,-mfpmath=sse,-msse,-msse2,-msse3,-O2) Seams that that was the problem, sorry for the noise. so... was it a sigill not a sigsegv? Cheers Jochen The parameters to _mm_set_epi32 look reasonable. The only reason I could imagine this failing is if your compiler isn't aligning things properly. cat /proc/cpuinfo processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz stepping : 11 cpu MHz: 1998.000 cache size : 4096 KB physical id: 0 siblings : 2 core id: 1 cpu cores : 2 apicid : 1 initial apicid : 1 fpu: yes fpu_exception : yes cpuid level: 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dts tpr_shadow vnmi flexpriority bogomips : 4654.98 clflush size : 64 cache_alignment: 64 address sizes : 36 bits physical, 48 bits virtual power management: bt attached. Cheers Jochen #0 0x7fa75897cbce in waitpid () #from /lib/x86_64-linux-gnu/libpthread.so.0 1 0x00435961 in #e_alert_show (sig=optimized out) at e_alert.c:57 2signal handler #called 3 0x7fa75b037cc5 in _mm_set_epi32 (__q0=255, __q1=255, #called __q2=255, __q3=255) #called at /usr/lib/gcc/x86_64-linux-gnu/4.6/include/emmintrin.h:586 #4 _op_blend_mas_can_dp_sse3 (s=optimized out, m=0x1e7a4e1 \377\377\377 #\377\377\377, c=4278190080, d=0x7fa74c8b0df0, l=4) at #op_blend_mask_color_sse3.c:79 5 0x7fa75b01c147 in #evas_common_font_draw_internal (dst=0x2268b70, dc=0x21c0eb0, x=29, y=12, #text_props=0x21c4718, func=0x7fa75b037850_op_blend_mas_can_dp_sse3, ext_x=29, ext_y=2, ext_w=313, ext_h=15, im_w=377, fn=optimized out, im_h=optimized out) at evas_font_draw.c:298 #6 0x7fa75b01c4cb in evas_common_font_draw (dst=0x2268b70, #dc=0x21c0eb0, fn=optimized out, x=29, y=12, text_props=0x21c4718) at #evas_font_draw.c:418 7 0x7fa74f3893ea in eng_font_draw #(data=optimized out, context=optimized out, surface=optimized out, #font=optimized out, x=optimized out, y=optimized out, w=313, h=15, ow=313, oh=15, text_props=0x21c4718) at evas_engine.c:898 #8 0x7fa75afd609f in evas_object_text_render (obj=0x214e480, #output=0x21c1380, context=0x21c0eb0, surface=0x2268b70, x=0, y=0) at #evas_object_text.c:1665 9 0x7fa75afebd3e in evas_render_mapped #(e=0x21c37a0, obj=0x214e480, context=0x21c0eb0, surface=0x2268b70, #off_x=0, off_y=0, mapped=0, ecx=0, ecy=0, ecw=377, ech=22) at evas_render.c:1256 #10 0x7fa75afeeaf1 in evas_render_updates_internal (e=0x21c37a0, #make_updates=1 '\001', do_draw=1 '\001') at evas_render.c:1579 11 #0x7fa75a911d65 in _ecore_evas_x_render (ee=0x21c3580) at #ecore_evas_x.c:256 12 0x7fa75a90f041 in _ecore_evas_idle_enter #(data=optimized out) at ecore_evas.c:52 13 0x7fa75ad6c1de in #_ecore_call_task_cb (data=optimized out, func=optimized out) at #ecore_private.h:246 14 _ecore_idle_enterer_call () at #ecore_idle_enterer.c:165 15 0x7fa75ad6daf5 in #_ecore_main_loop_iterate_internal (once_only=0) at ecore_main.c:1699 16 #0x7fa75ad6debf in ecore_main_loop_begin () at ecore_main.c:864 17 #0x00433bf7 in main (argc=optimized out, argv=optimized out) #at e_main.c:954 quit A debugging session is active. Inferior 1 [process 2371] will be detached. Quit anyway? (y or n) Detaching from program: /opt/e17/bin/enlightenment, process 2371 -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net
Re: [E-devel] e17 segfault on fresh install
On Mon, 17 Oct 2011 10:57:59 +1100 Jochen Schröder cycoma...@gmail.com said: On 10/17/2011 10:51 AM, Carsten Haitzler (The Rasterman) wrote: On Mon, 17 Oct 2011 10:43:46 +1100 Jochen Schrödercycoma...@gmail.com said: On 10/15/2011 04:20 AM, Jim Kukunas wrote: On Fri, Oct 14, 2011 at 03:18:48PM +1100, Jochen Schröder wrote: Hi all, I just rebuild all of EFL and E17 gives me a segfault when starting with a clean config directory. Seems to be related to the recent sse3 work. What is your compiler version and CFLAGS? Just realised my CFLAGS contained -msse4 (probably from when I copied the build script over from a different PC). I just recompiled without -msse4 and it is working now (cflags: -g3,-ggdb,-march=core2,-mfpmath=sse,-msse,-msse2,-msse3,-O2) Seams that that was the problem, sorry for the noise. so... was it a sigill not a sigsegv? I remember it being a sigsegv, I could recompile with sse4 to check. well -msse4 will tell the compiler to optimize FOR sse4 instructions - ie maybe use them automatically. this is going to hurt that machine of yours... it has no sse4. so bugs waiting to happen there - but these bugs sould show themselves as sigills not segv's. which is odd if you got a segv. Cheers Jochen The parameters to _mm_set_epi32 look reasonable. The only reason I could imagine this failing is if your compiler isn't aligning things properly. cat /proc/cpuinfo processor: 1 vendor_id: GenuineIntel cpu family : 6 model: 15 model name : Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz stepping : 11 cpu MHz : 1998.000 cache size : 4096 KB physical id : 0 siblings : 2 core id : 1 cpu cores: 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception: yes cpuid level : 10 wp : yes flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dts tpr_shadow vnmi flexpriority bogomips : 4654.98 clflush size : 64 cache_alignment : 64 address sizes: 36 bits physical, 48 bits virtual power management: bt attached. Cheers Jochen #0 0x7fa75897cbce in waitpid () #from /lib/x86_64-linux-gnu/libpthread.so.0 1 0x00435961 in #e_alert_show (sig=optimized out) at e_alert.c:57 2signal handler #called 3 0x7fa75b037cc5 in _mm_set_epi32 (__q0=255, __q1=255, #called __q2=255, __q3=255) #called at /usr/lib/gcc/x86_64-linux-gnu/4.6/include/emmintrin.h:586 #4 _op_blend_mas_can_dp_sse3 (s=optimized out, m=0x1e7a4e1 \377\377 #\377 \377\377\377, c=4278190080, d=0x7fa74c8b0df0, l=4) at #op_blend_mask_color_sse3.c:79 5 0x7fa75b01c147 in #evas_common_font_draw_internal (dst=0x2268b70, dc=0x21c0eb0, x=29, y=12, #text_props=0x21c4718, func=0x7fa75b037850_op_blend_mas_can_dp_sse3, ext_x=29, ext_y=2, ext_w=313, ext_h=15, im_w=377, fn=optimized out, im_h=optimized out) at evas_font_draw.c:298 #6 0x7fa75b01c4cb in evas_common_font_draw (dst=0x2268b70, #dc=0x21c0eb0, fn=optimized out, x=29, y=12, text_props=0x21c4718) at #evas_font_draw.c:418 7 0x7fa74f3893ea in eng_font_draw #(data=optimized out, context=optimized out, surface=optimized out, #font=optimized out, x=optimized out, y=optimized out, w=313, h=15, ow=313, oh=15, text_props=0x21c4718) at evas_engine.c:898 #8 0x7fa75afd609f in evas_object_text_render (obj=0x214e480, #output=0x21c1380, context=0x21c0eb0, surface=0x2268b70, x=0, y=0) at #evas_object_text.c:1665 9 0x7fa75afebd3e in evas_render_mapped #(e=0x21c37a0, obj=0x214e480, context=0x21c0eb0, surface=0x2268b70, #off_x=0, off_y=0, mapped=0, ecx=0, ecy=0, ecw=377, ech=22) at evas_render.c:1256 #10 0x7fa75afeeaf1 in evas_render_updates_internal (e=0x21c37a0, #make_updates=1 '\001', do_draw=1 '\001') at evas_render.c:1579 11 #0x7fa75a911d65 in _ecore_evas_x_render (ee=0x21c3580) at #ecore_evas_x.c:256 12 0x7fa75a90f041 in _ecore_evas_idle_enter #(data=optimized out) at ecore_evas.c:52 13 0x7fa75ad6c1de in #_ecore_call_task_cb (data=optimized out, func=optimized out) at #ecore_private.h:246 14 _ecore_idle_enterer_call () at #ecore_idle_enterer.c:165 15 0x7fa75ad6daf5 in #_ecore_main_loop_iterate_internal (once_only=0) at ecore_main.c:1699 16 #0x7fa75ad6debf in ecore_main_loop_begin () at ecore_main.c:864 17 #0x00433bf7 in main (argc=optimized out, argv=optimized out) #at e_main.c:954 quit A debugging session is active. Inferior 1 [process 2371] will be detached. Quit anyway? (y or n) Detaching from program: /opt/e17/bin/enlightenment, process 2371
Re: [E-devel] e17 segfault on fresh install
On Sat, 15 Oct 2011 06:29:37 +0200 (CEST) Vincent Torri vto...@univ-evry.fr said: On Sat, 15 Oct 2011, Tom Hacohen wrote: On 14/10/11 19:20, Jim Kukunas wrote: What is your compiler version and CFLAGS? The parameters to _mm_set_epi32 look reasonable. The only reason I could imagine this failing is if your compiler isn't aligning things properly. It's the sse3 issue all over again. As you can see, his CPU doesn't support sse3 but sse3 code is called. raster told me that there is a check of sse3 availability at runtime. Maybe the check is buggy it works. i've tested it on a pentium-m. it works a charm. it has no sse3. way too old :) -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e17 segfault on fresh install
On Sat, 15 Oct 2011 16:13:07 +1100 Jochen Schröder cycoma...@gmail.com said: On 10/15/2011 01:37 PM, Carsten Haitzler (The Rasterman) wrote: On Fri, 14 Oct 2011 16:16:44 -0700 Jim Kukunas james.t.kuku...@linux.intel.com said: On Sat, Oct 15, 2011 at 12:54:00AM +0200, Tom Hacohen wrote: On 14/10/11 19:20, Jim Kukunas wrote: What is your compiler version and CFLAGS? The parameters to _mm_set_epi32 look reasonable. The only reason I could imagine this failing is if your compiler isn't aligning things properly. It's the sse3 issue all over again. As you can see, his CPU doesn't support sse3 but sse3 code is called. His CPU does support SSE3, hence the ``pni'' in his /proc/cpuinfo. let's eliminate first shall we. tomas - can you either --disable-cpu-sse3 when configuring evas, OR set EVAS_CPU_NO_SSE3=1 as an env var before running e to see if this is sse3 stuff or not or a more generic problem. I assume you mean me not Tomas, as I reported the segfault. This was on oh god sorry. why did i say thomas? my mind was elsewhere on another email thread. :) my PC at work so it will have to wait until Monday. This is a Core 2 Duo, which AFAIK does support SSE3 (wikipedia says SSE3 was introduced with Prescott). you will have sse3 i am pretty sure. -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e17 segfault on fresh install
On Fri, 14 Oct 2011 23:19:21 -0700 Jim Kukunas james.t.kuku...@linux.intel.com wrote: On Sat, Oct 15, 2011 at 03:52:55PM +1000, David Seikel wrote: On Sat, 15 Oct 2011 16:13:07 +1100 Jochen Schröder cycoma...@gmail.com wrote: On 10/15/2011 01:37 PM, Carsten Haitzler (The Rasterman) wrote: On Fri, 14 Oct 2011 16:16:44 -0700 Jim Kukunas james.t.kuku...@linux.intel.com said: On Sat, Oct 15, 2011 at 12:54:00AM +0200, Tom Hacohen wrote: On 14/10/11 19:20, Jim Kukunas wrote: What is your compiler version and CFLAGS? The parameters to _mm_set_epi32 look reasonable. The only reason I could imagine this failing is if your compiler isn't aligning things properly. It's the sse3 issue all over again. As you can see, his CPU doesn't support sse3 but sse3 code is called. His CPU does support SSE3, hence the ``pni'' in his /proc/cpuinfo. let's eliminate first shall we. tomas - can you either --disable-cpu-sse3 when configuring evas, OR set EVAS_CPU_NO_SSE3=1 as an env var before running e to see if this is sse3 stuff or not or a more generic problem. I assume you mean me not Tomas, as I reported the segfault. This was on my PC at work so it will have to wait until Monday. This is a Core 2 Duo, which AFAIK does support SSE3 (wikipedia says SSE3 was introduced with Prescott). It did say ssse3 in your flags, just not straight after sse2, it's two lines further down. flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dts tpr_shadow vnmi flexpriority Dunno about that extra 's' though. ssse3 != sse3. ssse3 adds instructions like palignr and horizontal operations. For what it's worth, mine says sse4a later in the flags after sse2, but no sse3. sse3 is represented by ``pni'' in /proc/cpuinfo. No wonder there is some confusion. lol -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world. signature.asc Description: PGP signature -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e17 segfault on fresh install
On Fri, Oct 14, 2011 at 03:18:48PM +1100, Jochen Schröder wrote: Hi all, I just rebuild all of EFL and E17 gives me a segfault when starting with a clean config directory. Seems to be related to the recent sse3 work. What is your compiler version and CFLAGS? The parameters to _mm_set_epi32 look reasonable. The only reason I could imagine this failing is if your compiler isn't aligning things properly. cat /proc/cpuinfo processor : 1 vendor_id : GenuineIntel cpu family: 6 model : 15 model name: Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz stepping : 11 cpu MHz : 1998.000 cache size: 4096 KB physical id : 0 siblings : 2 core id : 1 cpu cores : 2 apicid: 1 initial apicid: 1 fpu : yes fpu_exception : yes cpuid level : 10 wp: yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dts tpr_shadow vnmi flexpriority bogomips : 4654.98 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: bt attached. Cheers Jochen #0 0x7fa75897cbce in waitpid () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00435961 in e_alert_show (sig=optimized out) at e_alert.c:57 #2 signal handler called #3 0x7fa75b037cc5 in _mm_set_epi32 (__q0=255, __q1=255, __q2=255, __q3=255) at /usr/lib/gcc/x86_64-linux-gnu/4.6/include/emmintrin.h:586 #4 _op_blend_mas_can_dp_sse3 (s=optimized out, m=0x1e7a4e1 \377\377\377\377\377\377, c=4278190080, d=0x7fa74c8b0df0, l=4) at op_blend_mask_color_sse3.c:79 #5 0x7fa75b01c147 in evas_common_font_draw_internal (dst=0x2268b70, dc=0x21c0eb0, x=29, y=12, text_props=0x21c4718, func=0x7fa75b037850 _op_blend_mas_can_dp_sse3, ext_x=29, ext_y=2, ext_w=313, ext_h=15, im_w=377, fn=optimized out, im_h=optimized out) at evas_font_draw.c:298 #6 0x7fa75b01c4cb in evas_common_font_draw (dst=0x2268b70, dc=0x21c0eb0, fn=optimized out, x=29, y=12, text_props=0x21c4718) at evas_font_draw.c:418 #7 0x7fa74f3893ea in eng_font_draw (data=optimized out, context=optimized out, surface=optimized out, font=optimized out, x=optimized out, y=optimized out, w=313, h=15, ow=313, oh=15, text_props=0x21c4718) at evas_engine.c:898 #8 0x7fa75afd609f in evas_object_text_render (obj=0x214e480, output=0x21c1380, context=0x21c0eb0, surface=0x2268b70, x=0, y=0) at evas_object_text.c:1665 #9 0x7fa75afebd3e in evas_render_mapped (e=0x21c37a0, obj=0x214e480, context=0x21c0eb0, surface=0x2268b70, off_x=0, off_y=0, mapped=0, ecx=0, ecy=0, ecw=377, ech=22) at evas_render.c:1256 #10 0x7fa75afeeaf1 in evas_render_updates_internal (e=0x21c37a0, make_updates=1 '\001', do_draw=1 '\001') at evas_render.c:1579 #11 0x7fa75a911d65 in _ecore_evas_x_render (ee=0x21c3580) at ecore_evas_x.c:256 #12 0x7fa75a90f041 in _ecore_evas_idle_enter (data=optimized out) at ecore_evas.c:52 #13 0x7fa75ad6c1de in _ecore_call_task_cb (data=optimized out, func=optimized out) at ecore_private.h:246 #14 _ecore_idle_enterer_call () at ecore_idle_enterer.c:165 #15 0x7fa75ad6daf5 in _ecore_main_loop_iterate_internal (once_only=0) at ecore_main.c:1699 #16 0x7fa75ad6debf in ecore_main_loop_begin () at ecore_main.c:864 #17 0x00433bf7 in main (argc=optimized out, argv=optimized out) at e_main.c:954 quit A debugging session is active. Inferior 1 [process 2371] will be detached. Quit anyway? (y or n) Detaching from program: /opt/e17/bin/enlightenment, process 2371 -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Jim Kukunas Intel Open Source Technology Center -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list
Re: [E-devel] e17 segfault on fresh install
On 14/10/11 19:20, Jim Kukunas wrote: What is your compiler version and CFLAGS? The parameters to _mm_set_epi32 look reasonable. The only reason I could imagine this failing is if your compiler isn't aligning things properly. It's the sse3 issue all over again. As you can see, his CPU doesn't support sse3 but sse3 code is called. FFS, we should either fix this or remove it, but we can't just leave this broken sse3 support as is. It does more harm than good. -- Tom. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e17 segfault on fresh install
On Sat, Oct 15, 2011 at 12:54:00AM +0200, Tom Hacohen wrote: On 14/10/11 19:20, Jim Kukunas wrote: What is your compiler version and CFLAGS? The parameters to _mm_set_epi32 look reasonable. The only reason I could imagine this failing is if your compiler isn't aligning things properly. It's the sse3 issue all over again. As you can see, his CPU doesn't support sse3 but sse3 code is called. His CPU does support SSE3, hence the ``pni'' in his /proc/cpuinfo. FFS, we should either fix this or remove it, but we can't just leave this broken sse3 support as is. It does more harm than good. -- Tom. -- Jim Kukunas Intel Open Source Technology Center -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e17 segfault on fresh install
On Fri, 14 Oct 2011 16:16:44 -0700 Jim Kukunas james.t.kuku...@linux.intel.com said: On Sat, Oct 15, 2011 at 12:54:00AM +0200, Tom Hacohen wrote: On 14/10/11 19:20, Jim Kukunas wrote: What is your compiler version and CFLAGS? The parameters to _mm_set_epi32 look reasonable. The only reason I could imagine this failing is if your compiler isn't aligning things properly. It's the sse3 issue all over again. As you can see, his CPU doesn't support sse3 but sse3 code is called. His CPU does support SSE3, hence the ``pni'' in his /proc/cpuinfo. let's eliminate first shall we. tomas - can you either --disable-cpu-sse3 when configuring evas, OR set EVAS_CPU_NO_SSE3=1 as an env var before running e to see if this is sse3 stuff or not or a more generic problem. -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e17 segfault on fresh install
On Sat, 15 Oct 2011, Tom Hacohen wrote: On 14/10/11 19:20, Jim Kukunas wrote: What is your compiler version and CFLAGS? The parameters to _mm_set_epi32 look reasonable. The only reason I could imagine this failing is if your compiler isn't aligning things properly. It's the sse3 issue all over again. As you can see, his CPU doesn't support sse3 but sse3 code is called. raster told me that there is a check of sse3 availability at runtime. Maybe the check is buggy Vincent FFS, we should either fix this or remove it, but we can't just leave this broken sse3 support as is. It does more harm than good. -- Tom. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e17 segfault on fresh install
On 10/15/2011 01:37 PM, Carsten Haitzler (The Rasterman) wrote: On Fri, 14 Oct 2011 16:16:44 -0700 Jim Kukunas james.t.kuku...@linux.intel.com said: On Sat, Oct 15, 2011 at 12:54:00AM +0200, Tom Hacohen wrote: On 14/10/11 19:20, Jim Kukunas wrote: What is your compiler version and CFLAGS? The parameters to _mm_set_epi32 look reasonable. The only reason I could imagine this failing is if your compiler isn't aligning things properly. It's the sse3 issue all over again. As you can see, his CPU doesn't support sse3 but sse3 code is called. His CPU does support SSE3, hence the ``pni'' in his /proc/cpuinfo. let's eliminate first shall we. tomas - can you either --disable-cpu-sse3 when configuring evas, OR set EVAS_CPU_NO_SSE3=1 as an env var before running e to see if this is sse3 stuff or not or a more generic problem. I assume you mean me not Tomas, as I reported the segfault. This was on my PC at work so it will have to wait until Monday. This is a Core 2 Duo, which AFAIK does support SSE3 (wikipedia says SSE3 was introduced with Prescott). Cheers Jochen -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] e17 segfault on fresh install
On Sat, 15 Oct 2011 16:13:07 +1100 Jochen Schröder cycoma...@gmail.com wrote: On 10/15/2011 01:37 PM, Carsten Haitzler (The Rasterman) wrote: On Fri, 14 Oct 2011 16:16:44 -0700 Jim Kukunas james.t.kuku...@linux.intel.com said: On Sat, Oct 15, 2011 at 12:54:00AM +0200, Tom Hacohen wrote: On 14/10/11 19:20, Jim Kukunas wrote: What is your compiler version and CFLAGS? The parameters to _mm_set_epi32 look reasonable. The only reason I could imagine this failing is if your compiler isn't aligning things properly. It's the sse3 issue all over again. As you can see, his CPU doesn't support sse3 but sse3 code is called. His CPU does support SSE3, hence the ``pni'' in his /proc/cpuinfo. let's eliminate first shall we. tomas - can you either --disable-cpu-sse3 when configuring evas, OR set EVAS_CPU_NO_SSE3=1 as an env var before running e to see if this is sse3 stuff or not or a more generic problem. I assume you mean me not Tomas, as I reported the segfault. This was on my PC at work so it will have to wait until Monday. This is a Core 2 Duo, which AFAIK does support SSE3 (wikipedia says SSE3 was introduced with Prescott). It did say ssse3 in your flags, just not straight after sse2, it's two lines further down. flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dts tpr_shadow vnmi flexpriority Dunno about that extra 's' though. For what it's worth, mine says sse4a later in the flags after sse2, but no sse3. -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world. signature.asc Description: PGP signature -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
