On Thu, Sep 20, 2012 at 04:23:11PM +0200, Tomas Cech wrote:
Hi,I have finally got to run edje_cc in valgrind and here is the output: valgrind -- /r/n/idie_cc -id ../../../src/modules/illume2/images -DLOWRES_PDA=1 -DMEDIUMRES_PDA=2 -DHIRES_PDA=3 -DSLOW_PC=4 -DMEDIUM_PC=5 -DFAST_PC=6 -DE17_PROFILE=SLOW_PC ../../../src/modules/illume2/e-module-illume2.edc ../../../src/modules/illume2/e-module-illume2.edj ==50716== Memcheck, a memory error detector ==50716== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al. ==50716== Using Valgrind-3.8.0 and LibVEX; rerun with -h for copyright info ==50716== Command: /usr/bin/edje_cc -id ../../../src/modules/illume2/images -DLOWRES_PDA=1 -DMEDIUMRES_PDA=2 -DHIRES_PDA=3 -DSLOW_PC=4 -DMEDIUM_PC=5 -DFAST_PC=6 -DE17_PROFILE=SLOW_PC ../../../src/modules/illume2/e-module-illume2.edc ../../../src/modules/illume2/e-module-illume2.edj ==50716== ==50716== Invalid read of size 4 ==50716== at 0x418A4F4: eet_data_image_encode_cipher (in /usr/lib64/libeet.so.1.7.99) ==50716== by 0x418A5A7: eet_data_image_encode (in /usr/lib64/libeet.so.1.7.99) ==50716== by 0x418A62F: eet_data_image_write_cipher (in /usr/lib64/libeet.so.1.7.99) ==50716== by 0x418A717: eet_data_image_write (in /usr/lib64/libeet.so.1.7.99) ==50716== by 0x10006947: data_thread_image (edje_cc_out.c:711) ==50716== by 0x100075C3: data_image_preload_done (edje_cc_out.c:784) ==50716== by 0x1000A3CB: data_write_images (edje_cc_out.c:863) ==50716== by 0x1000B5BB: data_write (edje_cc_out.c:1615) ==50716== by 0x10004773: main (edje_cc.c:330) ==50716== Address 0x5daa07c is 4,076 bytes inside a block of size 4,079 alloc'd ==50716== at 0x4068ED4: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-ppc64-linux.so) ==50716== by 0x418A483: eet_data_image_encode_cipher (in /usr/lib64/libeet.so.1.7.99) ==50716== by 0x418A5A7: eet_data_image_encode (in /usr/lib64/libeet.so.1.7.99) ==50716== by 0x418A62F: eet_data_image_write_cipher (in /usr/lib64/libeet.so.1.7.99) ==50716== by 0x418A717: eet_data_image_write (in /usr/lib64/libeet.so.1.7.99) ==50716== by 0x10006947: data_thread_image (edje_cc_out.c:711) ==50716== by 0x100075C3: data_image_preload_done (edje_cc_out.c:784) ==50716== by 0x1000A3CB: data_write_images (edje_cc_out.c:863) ==50716== by 0x1000B5BB: data_write (edje_cc_out.c:1615) ==50716== by 0x10004773: main (edje_cc.c:330) ==50716== ==50716== Invalid write of size 4 ==50716== at 0x418A4F8: eet_data_image_encode_cipher (in /usr/lib64/libeet.so.1.7.99) ==50716== by 0x418A5A7: eet_data_image_encode (in /usr/lib64/libeet.so.1.7.99) ==50716== by 0x418A62F: eet_data_image_write_cipher (in /usr/lib64/libeet.so.1.7.99) ==50716== by 0x418A717: eet_data_image_write (in /usr/lib64/libeet.so.1.7.99) ==50716== by 0x10006947: data_thread_image (edje_cc_out.c:711) ==50716== by 0x100075C3: data_image_preload_done (edje_cc_out.c:784) ==50716== by 0x1000A3CB: data_write_images (edje_cc_out.c:863) ==50716== by 0x1000B5BB: data_write (edje_cc_out.c:1615) ==50716== by 0x10004773: main (edje_cc.c:330) ==50716== Address 0x5daa07c is 4,076 bytes inside a block of size 4,079 alloc'd ==50716== at 0x4068ED4: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-ppc64-linux.so) ==50716== by 0x418A483: eet_data_image_encode_cipher (in /usr/lib64/libeet.so.1.7.99) ==50716== by 0x418A5A7: eet_data_image_encode (in /usr/lib64/libeet.so.1.7.99) ==50716== by 0x418A62F: eet_data_image_write_cipher (in /usr/lib64/libeet.so.1.7.99) ==50716== by 0x418A717: eet_data_image_write (in /usr/lib64/libeet.so.1.7.99) ==50716== by 0x10006947: data_thread_image (edje_cc_out.c:711) ==50716== by 0x100075C3: data_image_preload_done (edje_cc_out.c:784) ==50716== by 0x1000A3CB: data_write_images (edje_cc_out.c:863) ==50716== by 0x1000B5BB: data_write (edje_cc_out.c:1615) ==50716== by 0x10004773: main (edje_cc.c:330)==50716== --50716-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting--50716-- si_code=1; Faulting address: 0x6739AC98; sp: 0x4028ffb40 valgrind: the 'impossible' happened: Killed by fatal signal ==50716== at 0x3807E4D4: ??? (in /usr/lib64/valgrind/memcheck-ppc64-linux) ==50716== by 0x380C7D73: ??? (in /usr/lib64/valgrind/memcheck-ppc64-linux) ==50716== by 0x38031B4F: ??? (in /usr/lib64/valgrind/memcheck-ppc64-linux) ==50716== by 0x380CB34B: ??? (in /usr/lib64/valgrind/memcheck-ppc64-linux) ==50716== by 0x380E381F: ??? (in /usr/lib64/valgrind/memcheck-ppc64-linux) sched status: running_tid=1 Thread 1: status = VgTs_Runnable ==50716== at 0x4068ED4: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-ppc64-linux.so) ==50716== by 0x418F8FB: eet_write_cipher (in /usr/lib64/libeet.so.1.7.99) ==50716== by 0x418A657: eet_data_image_write_cipher (in /usr/lib64/libeet.so.1.7.99) ==50716== by 0x418A717: eet_data_image_write (in /usr/lib64/libeet.so.1.7.99) ==50716== by 0x10006947: data_thread_image (edje_cc_out.c:711) ==50716== by 0x100075C3: data_image_preload_done (edje_cc_out.c:784) ==50716== by 0x1000A3CB: data_write_images (edje_cc_out.c:863) ==50716== by 0x1000B5BB: data_write (edje_cc_out.c:1615) ==50716== by 0x10004773: main (edje_cc.c:330) Note: see also the FAQ in the source distribution. It contains workarounds to several common problems. In particular, if Valgrind aborted or crashed after identifying problems in your program, there's a good chance that fixing those problems will prevent Valgrind aborting or crashing, especially if it happened in m_mallocfree.c. If that doesn't help, please report this bug to: www.valgrind.org In the bug report, send all the above text, the valgrind version, and what OS and version you are using. Thanks. Is it all you need to be able to fix it or you need some more information? Best regards, Tomas Cech Sleep_Walker
This output seems to be more informative: http://sprunge.us/CfQc valgrind /usr/bin/edje_cc -id ../../../src/modules/illume2/images -DLOWRES_PDA=1 -DMEDIUMRES_PDA=2 -DHIRES_PDA=3 -DSLOW_PC=4 -DMEDIUM_PC=5 -DFAST_PC=6 -DE17_PROFILE=SLOW_PC \ ../../../src/modules/illume2/e-module-illume2.edc \ ../../../src/modules/illume2/e-module-illume2.edj valgrind: warning (non-fatal): readlink("/proc/self/exe") failed. valgrind: continuing, however --trace-children=yes will not work. --33927:0:aspacem Valgrind: FATAL: can't open /proc/self/maps --33927:0:aspacem Exiting now. wolfberry-1:~/rpmbuild/BUILD/enlightenment-0.16.999.76763/src/modules/illume2> valgrind /usr/bin/edje_cc -id ../../../src/modules/illume2/images -DLOWRES_PDA=1 -DMEDIUMRES_PDA=2 -DHIRES_PDA=3 -DSLOW_PC=4 -DMEDIUM_PC=5 -DFAST_PC=6 -DE17_PROFILE=SLOW_PC ../../../src/modules/illume2/e-module-illume2.edc ../../../src/modules/illume2/e-module-illume2.edj ==38325== Memcheck, a memory error detector ==38325== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al. ==38325== Using Valgrind-3.8.0 and LibVEX; rerun with -h for copyright info ==38325== Command: /usr/bin/edje_cc -id ../../../src/modules/illume2/images -DLOWRES_PDA=1 -DMEDIUMRES_PDA=2 -DHIRES_PDA=3 -DSLOW_PC=4 -DMEDIUM_PC=5 -DFAST_PC=6 -DE17_PROFILE=SLOW_PC ../../../src/modules/illume2/e-module-illume2.edc ../../../src/modules/illume2/e-module-illume2.edj==38325== ==38325== Invalid read of size 4
==38325== at 0x418A4F4: eet_data_image_encode_cipher (eet_image.c:1302) ==38325== by 0x418A5A7: eet_data_image_encode (eet_image.c:1369) ==38325== by 0x418A62F: eet_data_image_write_cipher (eet_image.c:1104) ==38325== by 0x418A717: eet_data_image_write (eet_image.c:1128) ==38325== by 0x10006947: data_thread_image (edje_cc_out.c:711) ==38325== by 0x100075C3: data_image_preload_done (edje_cc_out.c:784) ==38325== by 0x1000A3CB: data_write_images (edje_cc_out.c:863) ==38325== by 0x1000B5BB: data_write (edje_cc_out.c:1615) ==38325== by 0x10004773: main (edje_cc.c:330) ==38325== Address 0x5daa07c is 4,076 bytes inside a block of size 4,079 alloc'd ==38325== at 0x4068ED4: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-ppc64-linux.so) ==38325== by 0x418A483: eet_data_image_encode_cipher (eet_image.c:786) ==38325== by 0x418A5A7: eet_data_image_encode (eet_image.c:1369) ==38325== by 0x418A62F: eet_data_image_write_cipher (eet_image.c:1104) ==38325== by 0x418A717: eet_data_image_write (eet_image.c:1128) ==38325== by 0x10006947: data_thread_image (edje_cc_out.c:711) ==38325== by 0x100075C3: data_image_preload_done (edje_cc_out.c:784) ==38325== by 0x1000A3CB: data_write_images (edje_cc_out.c:863) ==38325== by 0x1000B5BB: data_write (edje_cc_out.c:1615) ==38325== by 0x10004773: main (edje_cc.c:330)==38325== ==38325== Invalid write of size 4
==38325== at 0x418A4F8: eet_data_image_encode_cipher (eet_image.c:805) ==38325== by 0x418A5A7: eet_data_image_encode (eet_image.c:1369) ==38325== by 0x418A62F: eet_data_image_write_cipher (eet_image.c:1104) ==38325== by 0x418A717: eet_data_image_write (eet_image.c:1128) ==38325== by 0x10006947: data_thread_image (edje_cc_out.c:711) ==38325== by 0x100075C3: data_image_preload_done (edje_cc_out.c:784) ==38325== by 0x1000A3CB: data_write_images (edje_cc_out.c:863) ==38325== by 0x1000B5BB: data_write (edje_cc_out.c:1615) ==38325== by 0x10004773: main (edje_cc.c:330) ==38325== Address 0x5daa07c is 4,076 bytes inside a block of size 4,079 alloc'd ==38325== at 0x4068ED4: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-ppc64-linux.so) ==38325== by 0x418A483: eet_data_image_encode_cipher (eet_image.c:786) ==38325== by 0x418A5A7: eet_data_image_encode (eet_image.c:1369) ==38325== by 0x418A62F: eet_data_image_write_cipher (eet_image.c:1104) ==38325== by 0x418A717: eet_data_image_write (eet_image.c:1128) ==38325== by 0x10006947: data_thread_image (edje_cc_out.c:711) ==38325== by 0x100075C3: data_image_preload_done (edje_cc_out.c:784) ==38325== by 0x1000A3CB: data_write_images (edje_cc_out.c:863) ==38325== by 0x1000B5BB: data_write (edje_cc_out.c:1615) ==38325== by 0x10004773: main (edje_cc.c:330)==38325== --38325-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting
--38325-- si_code=1; Faulting address: 0x6739AC98; sp: 0x4028ffb40 valgrind: the 'impossible' happened: Killed by fatal signal ==38325== at 0x3807E4D4: ??? (in /usr/lib64/valgrind/memcheck-ppc64-linux) ==38325== by 0x380C7D73: ??? (in /usr/lib64/valgrind/memcheck-ppc64-linux) ==38325== by 0x38031B4F: ??? (in /usr/lib64/valgrind/memcheck-ppc64-linux) ==38325== by 0x380CB34B: ??? (in /usr/lib64/valgrind/memcheck-ppc64-linux) ==38325== by 0x380E381F: ??? (in /usr/lib64/valgrind/memcheck-ppc64-linux) sched status: running_tid=1 Thread 1: status = VgTs_Runnable ==38325== at 0x4068ED4: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-ppc64-linux.so) ==38325== by 0x418F8FB: eet_write_cipher (eet_lib.c:2330) ==38325== by 0x418A657: eet_data_image_write_cipher (eet_image.c:1109) ==38325== by 0x418A717: eet_data_image_write (eet_image.c:1128) ==38325== by 0x10006947: data_thread_image (edje_cc_out.c:711) ==38325== by 0x100075C3: data_image_preload_done (edje_cc_out.c:784) ==38325== by 0x1000A3CB: data_write_images (edje_cc_out.c:863) ==38325== by 0x1000B5BB: data_write (edje_cc_out.c:1615) ==38325== by 0x10004773: main (edje_cc.c:330) Note: see also the FAQ in the source distribution. It contains workarounds to several common problems. In particular, if Valgrind aborted or crashed after identifying problems in your program, there's a good chance that fixing those problems will prevent Valgrind aborting or crashing, especially if it happened in m_mallocfree.c. If that doesn't help, please report this bug to: www.valgrind.org In the bug report, send all the above text, the valgrind version, and what OS and version you are using. Thanks. Best regards, Tomas Cech Sleep_Walker
pgpoBlr042uuK.pgp
Description: PGP signature
------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html
_______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
