QGC SIGSEGV on Debian 8 x64

Ground Stations and utilities for Windows, Linux, Android, & others

QGC SIGSEGV on Debian 8 x64

Postby wangyeee » Mon Aug 17, 2015 4:07 am


When I was trying to compile QGC on Debian 8 x64 machine, the binary did not work. It crashed when I click connect button on the "Add Link" UI. All dependencies were installed by apt-get. I made a debug build and find out the error occurred on
Code: Select all
AQTelemetryView::initChart (this=0x233db50, uav= 0x263b530) at src/ui/aq_telemetryView.cpp:353

Here is the full stacktrace.
Code: Select all
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff31131a4 in QLayout::parentWidget() const ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
(gdb) bt
#0  0x00007ffff31131a4 in QLayout::parentWidget() const ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#1  0x00007ffff3113ffc in QLayout::addChildWidget(QWidget*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#2  0x00007ffff3111d9a in QGridLayout::addWidget(QWidget*, int, int, QFlags<Qt::AlignmentFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#3  0x0000000000761f13 in AQTelemetryView::initChart (this=0x233db50, uav=
    0x263b530) at src/ui/aq_telemetryView.cpp:353
#4  0x00000000007e699a in AQTelemetryView::qt_static_metacall (_o=0x233db50,
    _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0x7fffffffd490)
    at build/moc/moc_aq_telemetryView.cpp:116
#5  0x00007ffff1a69fdd in QMetaObject::activate(QObject*, int, int, void**) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00000000007c1df3 in UASManager::activeUASSet (this=0xfe9f80,
    _t1=0x263b530) at build/moc/moc_UASManager.cpp:361
#7  0x000000000054300a in UASManager::setActiveUAS (this=0xfe9f80,
    uas=0x263b530) at src/uas/UASManager.cc:397
#8  0x0000000000542ab3 in UASManager::addUAS (this=0xfe9f80, uas=0x263b530)
    at src/uas/UASManager.cc:282
#9  0x000000000063e609 in QGCMAVLinkUASFactory::createUAS (mavlink=0x13d8520,
    link=0x2578130, sysid=1, heartbeat=0x7fffffffd7f0, parent=0x0)
    at src/uas/QGCMAVLinkUASFactory.cc:61
#10 0x00000000005655a3 in MAVLinkProtocol::receiveBytes (this=0x13d8520,
    link=0x2578130, b=...) at src/comm/MAVLinkProtocol.cc:276
#11 0x00000000007c475d in MAVLinkProtocol::qt_static_metacall (_o=0x13d8520,
    _c=QMetaObject::InvokeMetaMethod, _id=14, _a=0x7fff8c00bf40)
    at build/moc/moc_MAVLinkProtocol.cpp:223
#12 0x00007ffff1a6aeda in QObject::event(QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007ffff30f412c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
    () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007ffff30f9600 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007ffff1a3adcb in QCoreApplication::notifyInternal(QObject*, QEvent*)
    () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007ffff1a3cdc3 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007ffff1a92da3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007fffeda46c5d in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007fffeda46f48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fffeda46ffc in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007ffff1a931b7 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007ffff1a38512 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>
) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x00007ffff1a4015c in QCoreApplication::exec() ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x000000000053ca37 in main (argc=1, argv=0x7fffffffe0e8) at src/main.cc:85

I did some search on Google and found someone reported similiar issue here:
https://groups.google.com/forum/#!topic ... bze9tweZh0
So I downloaded and installed latest Qt release(5.5) and retried to compile the code, but ended up with same error.

Any ideas about this?
Posts: 37
Joined: Sun Feb 22, 2015 5:20 am

Return to AQ Software

Who is online

Users browsing this forum: No registered users and 2 guests