Segv in latest stable version (1.3.2)

[vatsers]

I receive a Segv as soon as enlightenment starts (even still in splash screen) The system is not recoverable, since it continues to throw new segv's. I have had to revert to older svn to restore functionality

[vatsers]

output from startx

[cedric]

Reading startx log, it sounds like your ecore_evas or evas backend is not properly setup. What are the output of Evas and Ecore configure ?

What distro do you use ?

On what system ?

[vatsers]

I have attached the configure output from evas and ecore.

I am using opensuse 11.2 32bit kernel: Linux servalan 2.6.31.12-0.2-desktop #1 SMP PREEMPT 2010-03-16 21:25:39 +0100 i686 i686 i386 GNU/Linux

1x dual core Intel(R) Pentium(R) 4 CPU 3.00GHz Mem 1.5GB grphx: 01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AS [Radeon 9550] 01:00.1 Display controller: ATI Technologies Inc RV350 AS [Radeon 9550] (Secondary)

coder@servalan:~/trunk/evas> gcc -v Using built-in specs. Target: i586-suse-linux Configured with: ../configure --prefix=/usr --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib --libexecdir=/usr/lib --enable-languages=c,c++,objc,fortran,obj-c++,java,ada --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.4 --enable-ssp --disable-libssp --with-bugurl= http://bugs.opensuse.org/ --with-pkgversion='SUSE Linux' --disable-libgcj --disable-libmudflap --with-slibdir=/lib --with-system-zlib --enable-cxa_atexit --enable-libstdcxx-allocator=new --disable-libstdcxx-pch --enable-version-specific-runtime-libs --program-suffix=-4.4 --enable-linux-futex --without-system-libunwind --with-arch-32=i586 --with-tune=generic --build=i586-suse-linux Thread model: posix gcc version 4.4.1 [gcc-4_4-branch revision 150839] (SUSE Linux)

Please let me know if anything is not in order. However as I said, rolling back to previous svn (i.e. 49500) the system works.

[cedric]

Both configure seems good. Could you try by installing and running elementary_test application ?

The reason I am asking you to build it, is that the easiest app to get running that will use both ecore_evas and evas so we could perhaps understand better what's going on.

[vatsers]

I have attached errors and warnings when running elementary_test

The Anchorblock fails.

[cedric]

I don't understand what is going on ! Elementary seems to just work fine, except this strange string.

Could you try running E17 in a Xephyr window ? You can start Xephyr :1.0 first, then launch with gdb like this : ECORE_ERROR_ABORT=1 gdb enlightenment_start, and type "r -display :1.0" in the command line.

[vatsers]

I ran E17 in Xephyr as you instructed I have attached the output.

[vatsers]

Update: I installed on my laptop (also opensuse, but other hardware, 64bit, etc) It also fails in exactly the same manner.

[cedric]

Sorry I forgot to ask you to type bt when E abort in gdb.

Do you use opensuse package or any custom build script ?

Your laptop was a fresh install ?

[vatsers]

I have attched the backtrace.

I use the build script as it appears on the enlightenment site.

My laptop was not a fresh install, I just had not used the lastest svn since my other pc failed. I now installed the latest svn, it failed too, so I'm currently downloading older svn (44144) in order to restore operability

[cedric]

Sorry the backtrace didn't make it to the website.

Do you use something like easy_e17.sh ?

Their is something strange on your computer, all devs use up to date E17 svn, so it run on some PC. We just need to figure out why not on your computer.

[cedric]

Just checked when was r44144, it was 6 months old. Sadly around 5000commits happens since then... not that much help.

[vatsers]

I uploaded the script I use to compile E17

Maybe something is hidden in there

[cedric]

Well appart from ephoto that should not work build this way anymore, I don't see strange thing in your script (ephoto require elementary and ethumb now).

I just committed a patch in e17 that will make it run a little longer without a proper Ecore_Evas. Could you try svn r49996 ? (just rebuild e17).

Maybe you can also add EINA_LOG_LEVEL=3 in the environment variable before calling gdb.

[vatsers]

Unfortunately the problem persists.

I have attached the Xephyr and bt output using EINA_LOG_LEVEL=3

I can confirm that I got the laptop working with r49750

[cedric]

It seems it wasn't taking EINA_LOG_LEVEL into account.

Did you run it like that : "EINA_LOG_LEVEL=3 ECORE_ERROR_ABORT=1 gdb enlightenment_start" ?

[vatsers]

Good morning Cedric,

Sorry I couldn'y reply over the weekend.

I have attached the output you requested.

This is with the latest svn

[vatsers]

I have managed to determine that the problem appears when the pager module is enabled when using certain themes, such as cerium and bluegrass.

That would explain why nobody on the development team were experiencing the problem.

I also determined that, possible due to the same reason, when using these themes, the system module buttons did not work (power off, reboot etc etc)

So changing the theme has solved these issues. Now maybe you can determine what is used differently on those themes, and be able to detect the problem.

Thanks,

Robert

[cedric]

That's a good news ! I will have little time this week, but I have now some way to reproduce it. Thanks a lot for your help !

[vatsers]

I would like to thank you for all your help and all the time and effort you put into my problem,

The support I received from you was faster than even major industry players with paid support.

If there's ever any way I can help out with the project, please let me know.

Thanks again,

Robert

[cedric]

Ok, it should be fixed with svn 50198. Could you check if it's gone ?

[vatsers]

hi Cedric,

Yyes, the problem is fixed. I no longer receive Segv when enlightenment starts.

I won't be using those themes however since the power / reboot buttons are still not working on those themes.

Thanks :)