https://bugs.kde.org/show_bug.cgi?id=376418

            Bug ID: 376418
           Summary: EKOS bleeding crashes after slew
           Product: kstars
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: mutla...@ikarustech.com
          Reporter: h...@lambermont.dyndns.org
  Target Milestone: ---

kstars-bleeding of today, 5:16.12+201702112051~ubuntu16.04.1

I'm working on the 10micron INDI driver, but the issue I see now looks to be in
EKOS. I did the following to get here: give a slew command. That's all. kstars
crashes. remote indiserver continues.
When I reconnect kstars to the indiserver it crashes with this :

(gdb) bt
#0  0x000000000067d721 in EkosManager::updateMountStatus (this=0x39608e0,
    status=<optimized out>)
    at
/build/kstars-bleeding-24lYmp/kstars-bleeding-16.12+201702112051~ubuntu16.04.1/kstars/ekos/ekosmanager.cpp:1931
#1  0x00000000005b543a in EkosManager::qt_static_metacall (_o=<optimized out>,
    _c=<optimized out>, _id=<optimized out>, _a=<optimized out>)
    at
/build/kstars-bleeding-24lYmp/kstars-bleeding-16.12+201702112051~ubuntu16.04.1/obj-x86_64-linux-gnu/kstars/moc_ekosmanager.cpp:335
#2  0x00007ffff3b0cd2a in QMetaObject::activate(QObject*, int, int, void**) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x00000000005a3d51 in Ekos::Mount::newStatus (this=this@entry=0x4047a70,
    _t1=ISD::Telescope::MOUNT_TRACKING)
    at
/build/kstars-bleeding-24lYmp/kstars-bleeding-16.12+201702112051~ubuntu16.04.1/obj-x86_64-linux-gnu/kstars/moc_mount.cpp:355
#4  0x000000000070351e in Ekos::Mount::updateTelescopeCoords (this=0x4047a70)
    at
/build/kstars-bleeding-24lYmp/kstars-bleeding-16.12+201702112051~ubuntu16.04.1/kstars/ekos/mount/mount.cpp:243
#5  0x00000000005b6ce5 in Ekos::Mount::qt_static_metacall (_o=<optimized out>,
    _c=<optimized out>, _id=<optimized out>, _a=<optimized out>)
    at
/build/kstars-bleeding-24lYmp/kstars-bleeding-16.12+201702112051~ubuntu16.04.1/obj-x86_64-linux-gnu/kstars/moc_mount.cpp:225
#6  0x00007ffff3b0cd2a in QMetaObject::activate(QObject*, int, int, void**) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007ffff3b195c8 in QTimer::timerEvent(QTimerEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007ffff3b0dbb3 in QObject::event(QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x00007ffff48ba05c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x00007ffff48bf516 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x00007ffff3ade38b in QCoreApplication::notifyInternal(QObject*, QEvent*)
()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x00007ffff3b335ed in QTimerInfoList::activateTimers() ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007ffff3b33af1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007fffeecde197 in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x00007fffeecde3f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007fffeecde49c in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007ffff3b347eb in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEvent
sFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007ffff3adbb4a in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00007ffff3ae3bec in QCoreApplication::exec() ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x0000000000485b1b in main (argc=1, argv=<optimized out>)
    at
/build/kstars-bleeding-24lYmp/kstars-bleeding-16.12+201702112051~ubuntu16.04.1/kstars/main.cpp:278

As indiserver continues to run I think this is a bug in ekos. I hope above
helps

-- Hans

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to