On 14 February 2012 17:35, Cedric BAIL <cedric.b...@free.fr> wrote:
> On Tue, Feb 14, 2012 at 6:17 PM, Mark Dickie <blaeberr...@gmail.com>
> wrote:
> > On 14 February 2012 16:56, Cedric BAIL <cedric.b...@free.fr> wrote:
> >> On Tue, Feb 14, 2012 at 5:50 PM, Mark Dickie <blaeberr...@gmail.com>
> >> wrote:
> >> > Having a few errors with edje_cc on new builds of debian wheezy and
> >> ubuntu
> >> > precise. - same error with both:
> >> >
> >> > mark@eagle:~/Computer/e/e/src/modules/conf_randr$ edje_cc -v
> >> > e-module-conf_randr.edc
> >> > edje_cc: Wrote 303 bytes ( 0Kb) for "edje_file" header
> >> > Illegal instruction
> >> >
> >> > Using easy_e17, clean ubuntu headless build with dependencies from
> >> > http://trac.enlightenment.org/e/wiki/Ubuntu - only change is the
> upgrade
> >> > from libjpeg62 to libjpeg8
> >> >
> >> > uname -a
> >> > Linux eagle 3.2.0-15-generic-pae #24-Ubuntu SMP Tue Feb 7 23:30:35 UTC
> >> 2012
> >> > i686 athlon i386 GNU/Linux
> >> >
> >> > Glad to do any debugging as at the moment I can't even build e - boo
> hoo!
> >>
> >> Could you call edje_cc with valgrind and give us its report ?
> >>
> >
> > Attached..do you need any other flags?
>
> Sorry lost by source forge. Could you name it something like
> valgrind.txt with text mime type ?
> --
> Cedric BAIL
>
>
>
Hope this works
--
Mark Dickie
Tel (+44)
Email blaeberr...@gmail.com
Skype blaeberries
mark@eagle:~/Computer/e/e/src/modules/conf_randr$ valgrind edje_cc
e-module-conf_randr.edc ==4396== Memcheck, a memory error detector
==4396== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==4396== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==4396== Command: edje_cc e-module-conf_randr.edc
==4396==
vex x86->IR: unhandled instruction bytes: 0x66 0xF 0xEF 0xC0
==4396== valgrind: Unrecognised instruction at address 0x41fa922.
==4396== at 0x41FA922: _op_blend_pas_dp_sse3 (in
/usr/local/lib/libevas.so.1.1.99)
==4396== by 0x4219EC3: evas_common_op_sse3_test (in
/usr/local/lib/libevas.so.1.1.99)
==4396== by 0x41D7096: evas_common_cpu_sse3_test (in
/usr/local/lib/libevas.so.1.1.99)
==4396== by 0x41D71B2: evas_common_cpu_feature_test (in
/usr/local/lib/libevas.so.1.1.99)
==4396== by 0x41D7302: evas_common_cpu_init (in
/usr/local/lib/libevas.so.1.1.99)
==4396== by 0x4039F99: _output_setup (in
/usr/local/lib/evas/modules/engines/buffer/linux-gnu-i686-1.1.99/module.so)
==4396== by 0x403A267: eng_setup (in
/usr/local/lib/evas/modules/engines/buffer/linux-gnu-i686-1.1.99/module.so)
==4396== by 0x4157148: evas_engine_info_set (in
/usr/local/lib/libevas.so.1.1.99)
==4396== by 0x40F4BEF: ecore_evas_buffer_allocfunc_new (in
/usr/local/lib/libecore_evas.so.1.1.99)
==4396== by 0x40F48F5: ecore_evas_buffer_new (in
/usr/local/lib/libecore_evas.so.1.1.99)
==4396== by 0x804BA76: data_write_images (edje_cc_out.c:493)
==4396== by 0x804D08E: data_write (edje_cc_out.c:1196)
==4396== by 0x804A55E: main (edje_cc.c:240)
==4396== Your program just tried to execute an instruction that Valgrind
==4396== did not recognise. There are two possible reasons for this.
==4396== 1. Your program has a bug and erroneously jumped to a non-code
==4396== location. If you are running Memcheck and you just saw a
==4396== warning about a bad jump, it's probably your program's fault.
==4396== 2. The instruction is legitimate but Valgrind doesn't handle it,
==4396== i.e. it's Valgrind's fault. If you think this is the case or
==4396== you are not sure, please let us know and we'll try to fix it.
==4396== Either way, Valgrind will now raise a SIGILL signal which will
==4396== probably kill your program.
vex x86->IR: unhandled instruction bytes: 0x66 0xF 0x6E 0x8D
==4396== valgrind: Unrecognised instruction at address 0x4219a71.
==4396== at 0x4219A71: evas_common_op_blend_init_sse3 (in
/usr/local/lib/libevas.so.1.1.99)
==4396== by 0x41C45B4: op_blend_init (in /usr/local/lib/libevas.so.1.1.99)
==4396== by 0x41CB8CD: evas_common_blend_init (in
/usr/local/lib/libevas.so.1.1.99)
==4396== by 0x4039F9E: _output_setup (in
/usr/local/lib/evas/modules/engines/buffer/linux-gnu-i686-1.1.99/module.so)
==4396== by 0x403A267: eng_setup (in
/usr/local/lib/evas/modules/engines/buffer/linux-gnu-i686-1.1.99/module.so)
==4396== by 0x4157148: evas_engine_info_set (in
/usr/local/lib/libevas.so.1.1.99)
==4396== by 0x40F4BEF: ecore_evas_buffer_allocfunc_new (in
/usr/local/lib/libecore_evas.so.1.1.99)
==4396== by 0x40F48F5: ecore_evas_buffer_new (in
/usr/local/lib/libecore_evas.so.1.1.99)
==4396== by 0x804BA76: data_write_images (edje_cc_out.c:493)
==4396== by 0x804D08E: data_write (edje_cc_out.c:1196)
==4396== by 0x804A55E: main (edje_cc.c:240)
==4396== Your program just tried to execute an instruction that Valgrind
==4396== did not recognise. There are two possible reasons for this.
==4396== 1. Your program has a bug and erroneously jumped to a non-code
==4396== location. If you are running Memcheck and you just saw a
==4396== warning about a bad jump, it's probably your program's fault.
==4396== 2. The instruction is legitimate but Valgrind doesn't handle it,
==4396== i.e. it's Valgrind's fault. If you think this is the case or
==4396== you are not sure, please let us know and we'll try to fix it.
==4396== Either way, Valgrind will now raise a SIGILL signal which will
==4396== probably kill your program.
==4396==
==4396== Process terminating with default action of signal 4 (SIGILL)
==4396== Illegal opcode at address 0x4219A71
==4396== at 0x4219A71: evas_common_op_blend_init_sse3 (in
/usr/local/lib/libevas.so.1.1.99)
==4396== by 0x41C45B4: op_blend_init (in /usr/local/lib/libevas.so.1.1.99)
==4396== by 0x41CB8CD: evas_common_blend_init (in
/usr/local/lib/libevas.so.1.1.99)
==4396== by 0x4039F9E: _output_setup (in
/usr/local/lib/evas/modules/engines/buffer/linux-gnu-i686-1.1.99/module.so)
==4396== by 0x403A267: eng_setup (in
/usr/local/lib/evas/modules/engines/buffer/linux-gnu-i686-1.1.99/module.so)
==4396== by 0x4157148: evas_engine_info_set (in
/usr/local/lib/libevas.so.1.1.99)
==4396== by 0x40F4BEF: ecore_evas_buffer_allocfunc_new (in
/usr/local/lib/libecore_evas.so.1.1.99)
==4396== by 0x40F48F5: ecore_evas_buffer_new (in
/usr/local/lib/libecore_evas.so.1.1.99)
==4396== by 0x804BA76: data_write_images (edje_cc_out.c:493)
==4396== by 0x804D08E: data_write (edje_cc_out.c:1196)
==4396== by 0x804A55E: main (edje_cc.c:240)
==4396==
==4396== HEAP SUMMARY:
==4396== in use at exit: 246,591 bytes in 1,820 blocks
==4396== total heap usage: 8,836 allocs, 7,016 frees, 1,421,714 bytes
allocated
==4396==
==4396== LEAK SUMMARY:
==4396== definitely lost: 0 bytes in 0 blocks
==4396== indirectly lost: 0 bytes in 0 blocks
==4396== possibly lost: 0 bytes in 0 blocks
==4396== still reachable: 246,591 bytes in 1,820 blocks
==4396== suppressed: 0 bytes in 0 blocks
==4396== Rerun with --leak-check=full to see details of leaked memory
==4396==
==4396== For counts of detected and suppressed errors, rerun with: -v
==4396== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Illegal instruction
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users
