reporting back after a long while - ran last night the same polar alignment scenario with the latest Kstars build (2020-08-08T19:57:56Z), and the polar alignment still crashes with Toupcam GPCMOS01200KPB on Pi3. Please see the gdb backtrace below. I've changed cables, power supplies, etc with no apparent effect. I'm just wondering could this still be somehow related to the Toupcam driver behaving differently from the Altair drivers, e.g. ? At least one difference in the logs between Altair camera and this Toupcam is notion "This looks like a multi-color image: processing the first image plane only. (NAXIS=3)" - could this affect e.g. memory usage in the associated processing? I'm under the impression that "apt-get update && apt-get upgrade" updates also the drivers in Indi so I suppose that I'm using the latest ones.. Is there some way to run some other diagnostics beyond what I've done so far?

Many thanks for your great work on Kstars, it really rocks!


#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x739c7230 in __GI_abort () at abort.c:79
#2 0x73a1751c in __libc_message (action=<optimized out>, fmt=<optimized out>)
at ../sysdeps/posix/libc_fatal.c:181
#3 0x73a996fc in __GI___fortify_fail_abort (
msg=0x73ae052c "stack smashing detected") at fortify_fail.c:28
#4 0x73a996c0 in __stack_chk_fail () at stack_chk_fail.c:29
#5 0x0063e238 in FITSData::pixelToWCS (this=0x3fa4ce60,
this@entry=0x6863be80, wcsPixelPoint=..., wcsCoord=...)
at ./kstars/kstars/fitsviewer/fitsdata.cpp:1804
#6 0x0090036c in Ekos::Align::calculatePAHError (this=this@entry=0x405d1a0)
at ./kstars/kstars/ekos/align/align.cpp:5403
#7 0x009041ec in Ekos::Align::setWCSToggled (this=0x405d1a0,
result=<optimized out>) at ./kstars/kstars/ekos/align/align.cpp:5815
#8 0x74a3f380 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#9 0x006b73ac in FITSView::wcsToggled (this=this@entry=0x3c81138,
_t1=<optimized out>, _t1@entry=true)
at ./obj-arm-linux-gnueabihf/kstars/KStarsLib_autogen/GB6ZSSQLTO/moc_fitsview.cpp:343
#10 0x0062d700 in FITSView::syncWCSState (this=0x3c81138)
at ./kstars/kstars/fitsviewer/fitsview.cpp:1787
#11 0x006bd7d0 in FITSView::qt_static_metacall (_o=<optimized out>,
_c=<optimized out>, _id=<optimized out>, _a=<optimized out>)
at ./obj-arm-linux-gnueabihf/kstars/KStarsLib_autogen/GB6ZSSQLTO/moc_fitsview.cpp:220
#12 0x74a3f244 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#13 0x748667b8 in QFutureWatcherBase::event(QEvent*) ()
from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#14 0x75334db4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5
#15 0x7533d2a8 in QApplication::notify(QObject*, QEvent*) ()
from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5
#16 0x03c81154 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)