https://bugs.kde.org/show_bug.cgi?id=447753
--- Comment #11 from Rob <rlanca...@gmail.com> --- Sorry I haven't been able to help you much with this so far. I have been super busy trying to make all the changes in my script and fix any issues that creates that I haven't been able to look at this yet. Also, I have a bunch of grading that I need to do. If it helps, one way that can really help to investigate the cause is to open it up in QT Creator or in Xcode and run the program with debugging turned on, then you get more information about what is going on when the crash occurs. I usually use my other repo for that, KStars-INDI-Mac-Dev, rather than kstars-on-osx-craft, because I like to keep the one repo for distribution and the other for development. The KStars-INDI-Mac-Dev can be a little tricky however, plus I will probably have to redo some of it after I get done with what I am doing to kstars-on-osx-craft. But, I do have a QT Creator project all set up right now with the latest KStars and INDI code using the KStars-INDI-Mac-Dev if I can do a debugging run or two to help you. Let me know what you want me to try. Also, It does look like you might be on to something. I don't have time right now to try to solve it, but I can run some tests. Also If it helps, I remember I was tracking down an intermittent bug a couple of months ago, I think it was in INDI Guide Simulator that might be similar to what you are checking out now, if I remember right, for some reason when INDI was starting up and properties were coming in, INDIListener received a property that either basically null or had inaccessible or bad data in it, which caused KStars to crash because it tried to access the bad data. I might have some of the screenshots of the debugging runs I did if it helps. -- You are receiving this mail because: You are watching all bug changes.
