That would be also interesting for me... I had in my last two sessions a sudden crash. All windows were closed... After restart of kstars everything was fine again...
Before the crash I did focusing, plate solving and took testpictures. Then I slewed to my objekt I want to photograph, start the session and BANG all closed...
Of course it would be terrific if you could help debug these crashes and improve our reliability.
Personally, I run kstars under gdb (e.g. gdb /usr/bin/kstars, then run) and get a backtrace (using the bt command in gdb) if the system crashes.
Then it's a question of looking there and at the output of debug logs (I always run with logs set to Verbose, File and all Ekos modules checked)
and getting a little more familiar with the source code. The logs on linux are saved in ~/.local/share/kstars/logs.
So it would be possible to run kstars with the ekos debugger and work as usual with it (is there any reduced e.g. speed, since I run stellarnmate on the Rasp 4B ?)? If I understood it right, then I click on save and upload the debugger file... If this is correct, I will run Kstars with the debugger.
The problem is, that the crash occurs occasionally and I didnt found a way to reproduce. but it happens roughly every 3rd or 4rth session especially when I'm preparing the session (focussing, plate solving, slewing to target and so on).
Once the session runs (taking pictures) I had no crash till now. I remeber only one time: there I run the focuser and after restarting the session it crashes...
Right, so Ekos Debugger is supposed to make this easy for those who don't know how to use gdb. Simply start KStars, and if it crashes, just click the save button. It will generate a zip file with the necessary logs that you can upload ans share with the developers.