Indeed, -D_FORTIFY_SOURCE=2 is set for Indi-3rdparty. I think I found the place where the memory violation is created.

Is there an option to catch this exception?

- Wolfgang

Read More...

Hi,
my newly developed INDI driver is functionally fine, but having it running an entire day shows this error:

2020-01-14T10:00:11: Driver indi_weatherradio: *** stack smashing detected ***: <unknown> terminated
2020-01-14T10:00:11: Driver indi_weatherradio: stderr EOF
<delProperty device="Weather Radio"/>
2020-01-14T10:00:11: Driver indi_weatherradio: restart #1
Child process 1650 died

Patch is on its way: phabricator.kde.org/D26263

Read More...

Hm, maybe that blocks the INDI client of EKOS. No clue where this comes from.

Read More...

OK, now I can see it. One thing that looks unusual: it looks like the EQMOD driver logs excessively. Could you please check which value is set as the polling period of your mount? I would recommend to set it to a value of 500ms or more.

If this does not help, I would at least try to set logging level to INFO. Maybe the explanation is simply excessive logging that leads to some blocking.

- Wolfgang

Read More...

Did you intentionally align with the ASI-120mm-s? Capturing the image during the alignment worked fine but it might be that it interferes with guiding.

- Wolfgang

Read More...