×

INDI Library v1.9.3 Released (11 Nov 2021)

Bimonthly Stable INDI Library release introduces new drivers and fixes for existing ones. Some highlights:

How to analyze Kstars crashes?

  • Posts: 20
  • Thank you received: 0
Now and then Kstars crashes more or less without any indication of why.
Is there a way of analyzing, is there a coredump to analyze or some other way?

++Håkan W++
3 months 2 weeks ago #74594

Please Log in or Create an account to join the conversation.

  • Posts: 75
  • Thank you received: 9
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...
3 months 2 weeks ago #74603

Please Log in or Create an account to join the conversation.

  • Posts: 728
  • Thank you received: 336
Håkan, Juergen,

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.

Jasem has put together an ekosdebugger to automate this, see indilib.org/forum/ekos/7245-new-tool-ekos-debugger.html

Hy
Orion Atlas Pro, William Optics ZS105, Moonlight V2 focuser, GSO RC10 w/RSF focuser
ZWO ASI1600, Astronomik Filters, ST80, QHY 5L-IIm guidecam.
KStars/Ekos/Indi on NUC10 & RPi4 w/SSD -- Ubuntu
Projects: Terrain, Polar Align, Analyze, Linear Focuser, SEP MultiStar & GPG Guide, FITS autostretch.
3 months 2 weeks ago #74623

Please Log in or Create an account to join the conversation.

  • Posts: 75
  • Thank you received: 9
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...
3 months 2 weeks ago #74624

Please Log in or Create an account to join the conversation.

  • Posts: 20
  • Thank you received: 0
Ok, I will start with gdb and take it from there.

Thanks for that tip!
3 months 2 weeks ago #74626

Please Log in or Create an account to join the conversation.

  • Posts: 728
  • Thank you received: 336
Juergen,
I find no slowdown when I run under gdb, so I imagine the same is true for ekosdebugger (which probably just runs gdb behind the scenes).
Hy
Orion Atlas Pro, William Optics ZS105, Moonlight V2 focuser, GSO RC10 w/RSF focuser
ZWO ASI1600, Astronomik Filters, ST80, QHY 5L-IIm guidecam.
KStars/Ekos/Indi on NUC10 & RPi4 w/SSD -- Ubuntu
Projects: Terrain, Polar Align, Analyze, Linear Focuser, SEP MultiStar & GPG Guide, FITS autostretch.
3 months 2 weeks ago #74627

Please Log in or Create an account to join the conversation.

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.
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
3 months 2 weeks ago #74628

Please Log in or Create an account to join the conversation.

Time to create page: 0.609 seconds