https://bugs.kde.org/show_bug.cgi?id=436583

Halla Rempt <ha...@valdyas.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ha...@valdyas.org

--- Comment #2 from Halla Rempt <ha...@valdyas.org> ---
It says the crashing thread is thread 1, but it's actually this bit:

Thread 32 (Thread 0x7f8d2498e700 (LWP 3411191)):
[KCrash Handler]
#4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#5  0x00007f8db7159859 in __GI_abort () at abort.c:79
#6  0x00007f8db71c43ee in __libc_message (action=action@entry=do_abort,
fmt=fmt@entry=0x7f8db72ee07c "*** %s ***: terminated\n") at
../sysdeps/posix/libc_fatal.c:155
#7  0x00007f8db7266b4a in __GI___fortify_fail (msg=msg@entry=0x7f8db72ee064
"stack smashing detected") at fortify_fail.c:26
#8  0x00007f8db7266b16 in __stack_chk_fail () at stack_chk_fail.c:24
#9  0x00007f8db7c04c1b in  () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#10 0x00007f8db7c04c4f in QImage::QImage(QSize const&, QImage::Format) () at
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#11 0x00007f8db7c04c8d in QImage::QImage(int, int, QImage::Format) () at
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#12 0x00007f8db7c05a22 in QImage::copy(QRect const&) const () at
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#13 0x00007f8db70e41f3 in QImage::copy(int, int, int, int) const (h=<optimized
out>, w=<optimized out>, y=-1, x=-1, this=0x7f8d2498d6f0) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qrect.h:184
#14 KisQImagePyramid::appendPyramidLevel(QImage const&) (this=0x7f8d6c2df560,
image=...) at /home/wolthera/krita/src/libs/brush/kis_qimage_pyramid.cpp:251
#15 0x00007f8db70e43c5 in KisQImagePyramid::KisQImagePyramid(QImage const&,
bool) (this=0x7f8d6c2df560, baseImage=..., useSmoothingForEnlarging=true) at
/home/wolthera/krita/src/libs/brush/kis_qimage_pyramid.cpp:39

And that looks like our old friend, the Qt 5.15 QImage crash that also causes
the gbr test to fail.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to