Hiya, any raspi experts here? I compiled Qt 5.5 for Raspberry Pi. The results are acceptable. Eglfs, the framebuffers, and wayland work. That's all I need. However, something bothers me a bit. When I start a program with -platform xcb I immediately get a segfault, Here the core:
> Core was generated by `./analogclock'. > Program terminated with signal SIGSEGV, Segmentation fault. > #0 0xb44f5098 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () > from /usr/local/qt5pi/lib/libQt5XcbQpa.so.5 > (gdb) > (gdb) bt > #0 0xb44f5098 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () > from /usr/local/qt5pi/lib/libQt5XcbQpa.so.5 > #1 0xb44f59f0 in QXcbConnection::processXcbEvents() () from > /usr/local/qt5pi/lib/libQt5XcbQpa.so.5 > #2 0xb689f06c in QObject::event(QEvent*) () from > /usr/local/qt5pi/lib/libQt5Core.so.5 > #3 0xb6872ebc in QCoreApplication::notify(QObject*, QEvent*) () from > /usr/local/qt5pi/lib/libQt5Core.so.5 > #4 0xb6872fe8 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from > /usr/local/qt5pi/lib/libQt5Core.so.5 > #5 0xb6875b7c in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, > QThreadData*) () from /usr/local/qt5pi/lib/libQt5Core.so.5 > Backtrace stopped: previous frame identical to this frame (corrupt stack?) Maybe someone can do something with the backtrace, I can't. I know that xcb has problems with the Raspberry Pi egl implementation. https://bugreports.qt.io/browse/QTBUG-36551 What I don't know, if the crash is in any way related to this problem. But whatever the problem is, a segfault is evil. Of course, always possible, that it is my configuration. Therefore the question: Did anyone here compile Qt 5.5 for the RPi already? Guido _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
