Willem, I gave the mount model tool a detailed look. I was observing a single (non repeatable) crash of Ekos/KStars as well when using RST-135. Interestingly though is that a crash can be repeatably forced by either hitting "pause" during the automatic alignment routine or hitting "stop" no matter when. I tried it with simulator drivers only (no real hardware connected) and the same behaviour was observed. Can you please test this as well? It should occur by just opening the mount model tool and then hitting the stop button on the very bottom-right corner.
Ekos Debugger shows this when it happens:
Thread 1 "kstars" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0xb3a01230 in __GI_abort () at abort.c:79
#2 0x00816b3a in Ekos::MountModel::resetAlignmentProcedure (this=0x343b0c8) at ./kstars/ekos/align/mountmodel.cpp:992
#3 0xb4579380 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#4 0xb4ded104 in QAbstractButton::clicked(bool) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5
#5 0xb4ded340 in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5
Backtrace stopped: previous frame identical to this frame (corrupt stack?)I noticed a function "abort()" getting called in KStar's mountmodel.cpp "MountModel::resetAlignmentProcedure()" as well as in "MountModel::startStopAlignmentProcedure()" when hitting "pause". Maybe abort() is a little too harsh?
@Jasem: Any ideas on that? I think there's a bug in the mount modeling tool.
Read More...
© 2003-2022 by INDI Library. All rights reserved.