Ok, This is for the bleeding edge git installation. (Stable installation is on another computer by the way, with the same result). And disconnecting the joystick eliminates the crash.



Let me know if I can provide any other assistance.

Thank you.

As a follow up, per the suggestion from xsnrg I added debuginfo for q5-qtbase with the command: sudo dnf --enablerepo=fedora-debuginfo install qt5-qtbase-debuginfo

which will hopefully provide additional information.

running the gdb backtrace analysis as described here, fedoraproject.org/wiki/StackTraces, I get the attached backtrace log file:

Please use Ekos Debugger (sudo apt-get -y install ekos-debugger) and go to INDI tab --> then select the profile and finally the indi_joystick driver to debug, then run INDI. Then press RUN.

From KStars, edit the equipment profile and change it to LOCAL to REMOTE , but keep everything else as is. Then connect and if the joystick crashes, Ekos Debugger should have the proper backtrace.

Following those instructions on my Fedora 33 system, these app and debug logs were generated:

Sorry Ekos Debugger has a bug I just pushed a fix but I think it's going to take a day for the updated version to be build. Meanwhile, you can run this again manually:

Then connect from KStars and hopefully now we get a useful backtrace.

Since he is using the copr for Fedora,it _should have_ built and been made available minutes after your push to master. I, however, prevented this from happening because the build was still set up to point to my repository for testing, which of course did not change. I updated it to point to knro/ekosdebugger now, and kicked a build. The new package should be available in a couple minutes, and going forward, will be available a couple minutes after a push to master in knro/ekosdebugger.

Jim

Ok, it's hard to keep up with you guys! I'm attaching backtrace logs using both the command line suggestion from the moderator as well as from a newly updated ekosdebugger just to be sure I have the correct tools. I updated my ekosdebugger via dnf to version ekosdebugger-0.0.1.git-20201015134612.fc33.x86_64.

From command line. Just to verify: I issued the gdb command, then from elsewhere, I started kstars, loaded the joystick profile, and performed a connection upon which the joystick driver crashed. I then went back to the command line and cut and pasted the resulting backtrace:



Using the updated ekosdebugger, I obtained the following:




I hope this was helpful. Let me know.

Jim,

Are debug packages installed on Fedora? I don't see any symbols in the gdb backtrace.

They are not installed by default. I gave a command on how to add them for the base qt5-qtbase package, but there are probably others that would be helpful as well. If you know what package in particular, we can ask that he install additional debug packages.

Yes! I'd be happy to install whatever it takes. Sorry about the inconvenience; my goto distribution is Fedora and I wasn't aware that debugging would be more difficult there. But I have a dedicated laptop that can be used to iron this out so I don't mind adding a lot of debugging packages.

I added debuginfo for glibc and reran ekosdebugger. Hopefully this provides useful additional information. Log files attached.

So I see where the crash is occuring:
At joystick_st->button[joystick_ev->number] = joystick_ev->value, which suggest that joystick_ev->number is out of bounds for joystick_st->axis but not sure why. Should probably add an extra check there. Need to install QtCreator and then debug this carefully. If you can make Teamviewer available I can login remotely to investigate more.