https://bugs.kde.org/show_bug.cgi?id=385397
Bug ID: 385397
Summary: Crash (segfault) on startup at memmove
Product: kwin
Version: 5.10.5
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: core
Assignee: kwin-bugs-n...@kde.org
Reporter: ms...@gdssecurity.com
Target Milestone: ---
Created attachment 108186
--> https://bugs.kde.org/attachment.cgi?id=108186&action=edit
valgrind trace
Hi,
I have a full valgrind trace (attached), as it was reproducible. It's most
likely not a HW failure as when I managed to log out and log back in, it's fine
and my system has been fine before and since. Bunch of invalid reads in
valgrind, not good. Also some conditional jumps not initialized, but it's best
to take the first invalid read and see if fixing it fixes all the rest -- it
may do.
on the dmesg I could see this:
[258563.996832] kwin_wayland[6079]: segfault at 10 ip 00007faf766c9240 sp
00007fff561cfdc8 error 4 in libKF5WaylandClient.so.5.37.0[7faf76665000+a9000]
Obviously, the valgrind trace is signfificantly more detailed.
--
You are receiving this mail because:
You are watching all bug changes.
