Thanks for your help! I recompiled it with debug support, and tried debugging it, but the problem was gone. Just to check, I tried it again without debug support, and again, no problems. So I guess I must have made a mistake somewhere in installing edje or eet.
Whatever it was, it's gone now. Sincerely. Byrel On Sat, Jun 25, 2011 at 12:55 AM, Carsten Haitzler <ras...@rasterman.com>wrote: > On Sat, 25 Jun 2011 01:30:56 -0400 Byrel Mitchell < > byrel.mitch...@gmail.com> > said: > > 1. missing gdb debug (no line numbers) > 2. valgrind? :) > http://trac.enlightenment.org/e/wiki/Debugging > > > I've been running E17 for a few weeks now, and decided I wanted to try > using > > editje. Rather than being satisfied with just installing editje, I > started > > upgrading my entire E install to HEAD. :) Just for reference, I am using > > omicron's easy-E17.sh script for installing. > > > > > > I've compiled and installed successfully: > > > > E_dbus > > Ecore > > Edje > > Eet > > Eeze > > Efreet > > Eina > > Eio > > Embryo > > Evas > > Exchange > > > > and was working on compiling E. I was making it when I got a segmentation > > fault, compiling e-module-illume-keyboard.edc. I ran edje-cc with -v, and > > found that it was successfully writing all the images, and crashing on > the > > first collection entry. Here is the last portion of the output, followed > by > > a gdb backtrace: > > > > (snip) > > /usr/bin/edje_cc: Wrote 112 bytes ( 0Kb) for "edje/images/16" image entry > > "bt_dis_hilight.png" compress: [raw: 96.2%] [real: 18.8%] > > /usr/bin/edje_cc: Wrote 258 bytes ( 0Kb) for "edje/images/17" image entry > > "base_bg.png" compress: [raw: 68.4%] [real: -106.4%] > > /usr/bin/edje_cc: Wrote 514 bytes ( 1Kb) for "edje/images/18" image > entry > > "inset_sunk.png" compress: [raw: 88.9%] [real: -23.3%] > > /usr/bin/edje_cc: Wrote 167 bytes ( 0Kb) for "edje/collections/0" > collection > > entry > > > > > > Program received signal SIGSEGV, Segmentation fault. > > 0x00007ffff1e9db34 in _eet_hash_gen () from /usr/lib64/libee > > > > > > #0 0x00007ffff1e9db34 in _eet_hash_gen () from /usr/lib64/libeet.so.1 > > #1 0x00007ffff1e9b5e9 in eet_dictionary_string_add () > > from /usr/lib64/libeet.so.1 > > #2 0x00007ffff1e8dc63 in eet_data_put_string () from > /usr/lib64/libeet.so.1 > > #3 0x00007ffff1e8e7cf in eet_data_put_type () from /usr/lib64/libeet.so.1 > > #4 0x00007ffff1e9555c in eet_data_put_unknown () from > /usr/lib64/libeet.so.1 > > #5 0x00007ffff1e960b0 in _eet_data_descriptor_encode () > > from /usr/lib64/libeet.so.1 > > #6 0x00007ffff1e9559d in eet_data_put_unknown () from > /usr/lib64/libeet.so.1 > > #7 0x00007ffff1e960b0 in _eet_data_descriptor_encode () > > from /usr/lib64/libeet.so.1 > > #8 0x00007ffff1e9544a in eet_data_put_array () from > /usr/lib64/libeet.so.1 > > #9 0x00007ffff1e960b0 in _eet_data_descriptor_encode () > > from /usr/lib64/libeet.so.1 > > #10 0x00007ffff1e90056 in eet_data_write_cipher () from > > /usr/lib64/libeet.so.1 > > #11 0x00007ffff1e900ee in eet_data_write () from /usr/lib64/libeet.so.1 > > #12 0x0000000000405320 in data_write_groups () > > #13 0x0000000000406146 in data_write () > > #14 0x0000000000403be9 in main () > > > > > > I'm not very familiar with the edc format, so I'm not sure if there is a > > problem with the edc, with the make process, or with something I'm doing. > > Have any of seen this problem? Or do you have any ideas what I might do > to > > fix it? I noticed that this was recently changed from an edj distribution > to > > the current edc w/ files; should I try reverting that directory to the > edj? > > > > I'll be happy to provide any more information that could be helpful. > > > > Thanks in advance, > > Byrel > > > ------------------------------------------------------------------------------ > > 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-c1 > > _______________________________________________ > > enlightenment-users mailing list > > enlightenment-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/enlightenment-users > > > > > -- > ------------- 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-c1 _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
