On Mon, Jun 18, 2012 at 1:34 AM, Mick <michaelkintz...@gmail.com> wrote: > I haven't yet recompiled everything with -g to do in depth debugging but > something has changed since last weekend. On revision 72292 I get random > crashes when I try to start e17. Also, at random I may get a crash in the > middle of a session. > > I noticed that enlightenment and /usr/lib64/enlightenment/utils/eeze_scanner > are left hanging in ps when I drop into a console. > > A backtrace on enlightenment shows: > > #0 0x00007fc931c23eb3 in ?? () > #1 0x0000000000402a9e in ?? () > #2 0x0000000000000021 in ?? () > #3 0x00007fffbbacacc8 in ?? () > #4 0x0000000500000009 in ?? () > #5 0x00007fff00000006 in ?? () > #6 0x00007fc931b54e90 in ?? () > #7 0x00007fc931b5b6b8 in ?? () > #8 0x0000000000000000 in ?? () > > The eeze lib shows "no stack". > > Not sure if this helps at all, but I'm posting in case it is a known problem, > or others have also had crashes too.
Nop, this backtrace doesn't help at all. You may try by recompiling all efl + e with CFLAGS="-g -ggdb3". You can also try to run enlightenment with valgrind and see what it report (enlightenment_start -valgrind). -- Cedric BAIL ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
