Might have something to do with the crash I get on Pi 3 after second image in a sequence if I have fits viewer active or if I load a fits file and close the window:
#0 FITSData::loadWCS (this=0x344a178)
at /build/kstars-bleeding-kznYv7/kstars-bleeding-16.12+201702130759~ubuntu16.04.1/kstars/fitsviewer/fitsdata.cpp:2130
#1 0x0018e7e8 in QtConcurrent::StoredMemberFunctionPointerCall0<bool, FITSData>::runFunctor (this=0x328d918)
at /usr/include/arm-linux-gnueabihf/qt5/QtConcurrent/qtconcurrentstoredfunctioncall.h:183
#2 0x0006cec2 in QtConcurrent::RunFunctionTask<bool>::run (this=0x328d918)
at /usr/include/arm-linux-gnueabihf/qt5/QtConcurrent/qtconcurrentrunbase.h:102
#3 0x757c66ca in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#4 0x757c8b42 in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#5 0x762c75b4 in start_thread () from /lib/arm-linux-gnueabihf/libpthread.so.0
#6 0x75327aac in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
Sounds weird that it would call loadWCS when I
close the window. Also fits viewer says my fits doesn't have WCS info even though it does.
I tried debugging this on my own compiled kstars and the code in question is:
p->ra = world[0];
p->dec = world[1];
and the p pointer is invalid at this point. The p array is quite big one (width * height * 2 * sizeof(double), in this case 3326*2504*2*8 = around 127 megabytes) so I don't know if it's running out of memory or something... What is this huge array used for?