Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

Hi Qt embedded Application is getting crashed.



  • Hi,

    I am working embedded application(yocto linux 32 arm gcc).

    My application is getting crashed after some operations. After Back trace, it is pointing at 0x764f5818 in ?? () from /usr/lib/libQt5Qml.so.5 . I am anticipating it is because of qml since it is pointing at libQt5Qml.so.5 . I am using loader in qml. Please can anybody help me on this.

    Regards,
    Kadappa Pujari.


  • Moderators

    You need to provide far more information:

    • which Qt version?
    • does it also crash when you run your app on desktop?
    • what does debugger / valgrind / address sanitizer tell you about the crash?
    • have you tried simplifying the code, running a minimal sample app to verify that it works correctly?


  • Qt version is 5.12.3
    No It will not crash on desktop. It crashes on embedded device.
    Below is Back trace about crash.
    [Thread debugging using libthread_db enabled]
    Using host libthread_db library "/lib/libthread_db.so.1".
    Core was generated by `./Source -platform eglfs'.
    Program terminated with signal SIGSEGV, Segmentation fault.
    #0 0x6294a240 in ?? ()
    [Current thread is 1 (Thread 0x73492010 (LWP 1362))]
    (gdb) bt
    #0 0x6294a240 in ?? ()
    #1 0x764cc818 in ?? () from /usr/lib/libQt5Qml.so.5
    Backtrace stopped: previous frame identical to this frame (corrupt stack?)
    (gdb)

    have you tried simplifying the code, running a minimal sample app to verify that it works correctly? Yes I have tried it is working fine.


  • Qt Champions 2017

    Hope Qt version on the host & what you have embedded system are same. Ensure that version matches.


  • Moderators

    That stack trace does not say much. Try compiling your code with address sanitizer, it should print a better stack trace and crash info.

    If possible, upgrade Qt to newest version (in 5.12 branch that's 5.12.6), perhaps it is a bug in Qt and is already fixed.



  • Thanks Dheerendra and sierdzio. Issue is resolved.

    @sierdzio , yes you are correct, it is Qt issue in libQt5Qml.so.5.12.3 and it is fixed in libQt5Qml.so.5.12.5.

    Thanks,
    Kadappa Pujari


Log in to reply