https://bugs.kde.org/show_bug.cgi?id=430325
Matt Fagnani <matthew.fagn...@utoronto.ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
URL| |https://bugzilla.redhat.com
| |/show_bug.cgi?id=1907270
--- Comment #1 from Matt Fagnani <matthew.fagn...@utoronto.ca> ---
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.
--
You are receiving this mail because:
You are watching all bug changes.
