Open wannabecoffeenerd opened 1 month ago
Since the backtrace was pointing to a segfault in the QHY SDK, I downloaded the latest version of the QHY SDK and installed it. Runnng the SingleFrameMode
test app, I don't see any errors. Might this suggest that the issue lies in how GetQHYCCDSingleFrame
is called here: https://github.com/indilib/indi-3rdparty/blob/master/indi-qhy/qhy_ccd_test.cpp#L416?
Comparing it to what's in QHY SDK's SingleFrameSample.cpp
:
ret = GetQHYCCDSingleFrame(camhandle,&w,&h,&bpp,&channels,ImgData);
if(ret == QHYCCD_SUCCESS)
{
printf("GetQHYCCDSingleFrame succeess! \n");
}
else
{
printf("GetQHYCCDSingleFrame fail:%d\n",ret);
}
Looks the same and AFAICT how ImgData
and pImgData
and all the parameters are allocated and passed in are identical with the only minor exception being that the sample uses malloc
and qhy_ccd_test
uses new []
. Not a very actionable comment but hopefully is useful to someone that's more familiar with the code.
cc @knro for viz
Describe the bug
qhy_ccd_test
segfaults when used with a QHY268C camera when initiating a capture. The same thing happens with kstars/ekos only when capturing an image.Here are the full logs with a debug build of
qhy_ccd_test
from the 2.0.8 tag and a gdb backtrace:This looks like an error with an AVX2 vectorized memset used on an unaligned buffer based on the backtrace?
I ensured that I have the right version of
fxload
and that firmware is being properly loaded on the QHY camera and is detected properly withlsusb
:To Reproduce
Build
libqhy
andindi-qhy
in debug mode with version 2.0.8":Ensure QHY camera is connected and detected properly:
Run with gdb:
Expected behavior
qhy_ccd_test
should pass without errors.Desktop (please complete the following information):