| Summary: | kstars segmentation faulted in DetailDialog::createGeneralTab | ||
|---|---|---|---|
| Product: | [Applications] kstars | Reporter: | Matt Fagnani <matt.fagnani> |
| Component: | general | Assignee: | Jasem Mutlaq <mutlaqja> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | bernie, rdieter |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 3.4.3 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| URL: | https://bugzilla.redhat.com/show_bug.cgi?id=1907270 | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | gdb output when run on kstars followed by the crash with the full trace | ||
|
Description
Matt Fagnani
2020-12-13 04:51:45 UTC
Clicking on Pointing > Find Object, entering sagittarius in Filter by name, and selecting the Details button was all that was required for the crash to happen in further tries. When I ran kstars from konsole and under gdb, the following error was shown when the crash occurred. QWaylandShmBuffer: mmap failed (Invalid argument) Running kstars under gdb indicated that the pointer this in frame 0 pointed to an inaccessible address. (gdb) p this $1 = (DetailDialog * const) 0x555558b4ecc0 (gdb) x this 0x555558b4ecc0: 0x561463b8 (gdb) x 0x561463b8 0x561463b8: Cannot access memory at address 0x561463b8 I'm attaching the gdb output with the full trace. The pointer dso = 0x0 in frame 0 in DetailDialog::createGeneralTab in the full trace which might indicate a null pointer dereference happened at detaildialog.cpp:312 if (!dso->longname().isEmpty() && dso->longname() != dso->name()) Crashes with this trace happened with both of kstars-3.4.3-4.fc33 with LTO disabled due to the problem at https://bugzilla.redhat.com/show_bug.cgi?id=1881915 and kstars-3.4.3-5.fc33 with LTO enabled and -fPIC from koji. This problem isn't likely to be related to the LTO problem. The crash happened when I ran kstars on X in Plasma on Wayland with QT_QPA_PLATFORM=xcb kstars & so the problem probably isn't specific to Wayland. Created attachment 134068 [details]
gdb output when run on kstars followed by the crash with the full trace
Maybe this is related (same EINVAL error in mmap()): https://bugs.kde.org/show_bug.cgi?id=429967 Cannot reproduce. Please try with more recent KStars (e.g. 3.5.2) > Cannot reproduce. Please try with more recent KStars (e.g. 3.5.2) Fedora 34 is still shipping kstars 3.4.3, and even rawhide doesn't have the latest version: https://src.fedoraproject.org/rpms/kstars Did you test on a device with Intel graphics? Actually rawhide attempted to update to 3.5.2 one month ago: https://src.fedoraproject.org/rpms/kstars/c/7d370caa3efe7a6844517713b53e3e41b0bc11e1?branch=rawhide But something went wrong during the build (and I couldn't find the build.log): https://koji.fedoraproject.org/koji/taskinfo?taskID=63692520 (In reply to Jasem Mutlaq from comment #4) > Cannot reproduce. Please try with more recent KStars (e.g. 3.5.2) KStars 3.4.3 is the most recent available version in Fedora 34 and rawhide as Bernie wrote. I installed the KStars 3.5.3 beta flatpak with the following based on https://community.kde.org/Guidelines_and_HOWTOs/Flatpak flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo flatpak remote-add --if-not-exists kdeapps --from https://distribute.kde.org/kdeapps.flatpakrepo flatpak install kstars flatpak run org.kde.kstars QWaylandShmBuffer: mmap failed (Invalid argument) was shown many times in Konsole as KStars started. The crash didn't happen when clicking on Pointing > Find Object, entering sagittarius in Filter by name, and selecting the Details button. The problem might've been fixed in 3.5.3 beta or earlier. The system is using Fedora 34 Plasma installation with Plasma 5.21.4, KF 5.80.0, Qt 5.15.2 with an integrated AMD Radeon R5 GPU using the radeonsi mesa 21.0.2 driver Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! |