Hello all,
Testing the new KStars release, and found that the Polar Alignment tool still crashes, although this time I am able to reproduce this in the simulator (cloudy here, so cant test a real camera). To reproduce this error, set the CCD Simulator to 4096x3520 resolution and 3.8 pixel size. My scope is set to 530mm focal length, and 106mm of aperture.
Go through the Polar Alignment tool at 4x4 binning. You will notice that the wizard completes successfully. Now change to 1x1 binning, and you will get a SEGFAULT.
Thread 12 "Thread (pooled)" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffa77fe700 (LWP 32754)]
0x00007ffff2946eb3 in wcsp2s () from /usr/lib/x86_64-linux-gnu/libwcs.so.5
(gdb) bt
#0 0x00007ffff2946eb3 in wcsp2s () from /usr/lib/x86_64-linux-gnu/libwcs.so.5
#1 0x0000000000632394 in FITSData::loadWCS (this=0x39bb8e0)
at /build/kstars-bleeding-TwcTY5/kstars-bleeding-17.04+201703222145~ubuntu16.04.1/kstars/fitsviewer/fitsdata.cpp:2145
#2 0x000000000066577e in QtConcurrent::StoredMemberFunctionPointerCall0<bool, FITSData>::runFunctor (this=0x438d310)
at /usr/include/x86_64-linux-gnu/qt5/QtConcurrent/qtconcurrentstoredfunctioncall.h:183
#3 0x00000000004b650d in QtConcurrent::RunFunctionTask<bool>::run (
this=0x438d310)
at /usr/include/x86_64-linux-gnu/qt5/QtConcurrent/qtconcurrentrunbase.h:102
#4 0x00007ffff327d2d3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x00007ffff32807be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6 0x00007ffff49bf6ba in start_thread ()
from /lib/x86_64-linux-gnu/libpthread.so.0
#7 0x00007ffff1adc82d in clone () from /lib/x86_64-linux-gnu/libc.so.6
While its a bummer that I get the segfault using this resolution size at 1x1 binning, it is encouraging to see that it works fine at 4x4 binning (smaller image). The selected resolution isn't even as large as the camera I would be doing this with live (4656x3520) because the sim doesn't allow me to set it this high. Regardless of that, I expect that I would still see this crash using my live camera, as I had this issue in the previous version of KStars.
Is using 4x4 binning going to skew anything in the PA tool, or would this be fine as a workaround?
