I'm using the sbig st-8xe for the guiding, trying to test recent changes,
I had numerous full crashes while doing this, with nothing useful put into a debug log, unfortunately,. I also can't pinpoint specific behaviours I might have been doing to cause the issue. I got full crashes while the auto-guiding was going, plus when trying to capture. I can't recall any crashes while calibrating though.
I probably asked you this before, but are you using kstars-bleeding from PPA or GIT? If you're using the PPA version, install the debug symbols packages.
sudo apt-get install kstars-bleeding-dbg
I am also using a safer and much faster way to set pixel data, but I need it to test this today before I commit.
usually it is caught by the KDE crash handler, but just to be sure, run it through gdb
gdb
file kstars
start
If it asks you about temporary break point, just press c and enter. If KStars crashes, just go back to gdb and type in bt to get the backtrace which would help in debugging the issue.
I'll attach a stack-trace later, but if you hit the auto-guide and haven't got a star selected (no green box) - you'll crash the program. It probably shouldn't let you try to start auto-guiding and report an error in the logs.
I noticed in the LX200 Classic logs that I was getting a few messages about being unable to guide while moving - during calibration or guiding. Is this something to be concerned about?