This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux: qt samples -backend linuxfb on Sitara AM57XX

Tool/software: Linux

Hi, Running a sample from the qt samples. on linuxfb platform

The image appears on the screen then BUM...  

GNU gdb (Linaro GDB) 7.8-2014.09
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <gnu.org/.../gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabi".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://bugs.linaro.org>.
Find the GDB manual and other documentation resources online at:
<www.gnu.org/.../>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./calculator...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/share/qt5/examples/widgets/widgets/calculator/calculator
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
No such plugin for spec  "Auto"

Program received signal SIGSEGV, Segmentation fault.
__memcpy_neon () at ../ports/sysdeps/arm/armv7/multiarch/memcpy_impl.S:590
590    ../ports/sysdeps/arm/armv7/multiarch/memcpy_impl.S: No such file or directory.
(gdb) bt
#0  __memcpy_neon () at ../ports/sysdeps/arm/armv7/multiarch/memcpy_impl.S:590
Backtrace stopped: Cannot access memory at address 0x8081000
(gdb)

  • I had some progress. If I remove /lib/modules/X.X.X.X/<folders and files>,the above error is gone and linuxfb works great. lsmod shows nothing. Also the matrix-gui works, which I have never seen it until now.
    weston is still in jeopardy, starts and hangs, despite, before was reporting weird inconsistent errors. I guess I have to investigate slowly, starting from: roll back the gdb to 7.7.1 because the gdb has the 'linux-vdso.so.1' bug, and take it from there...
    I just was wondering, why Sitara processors has such bad support ?