https://bugs.kde.org/show_bug.cgi?id=462761
Alvin Wong <al...@alvinhc.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |al...@alvinhc.com
--- Comment #7 from Alvin Wong <al...@alvinhc.com> ---
Let's see... if you want to get some useful information out of gdb, you should
run the command `thread apply all bt` when stopped at the trap / fault, at
least that's what applies usually. However, the debug output does indicate it
is a heap use-after-free, so usual debugging techniques aren't going to be too
useful.
I have an automated Krita build with ASan^ which would do a lot more to help
diagnose this issue. You can get it from
https://github.com/alvinhochun/krita-build/actions (select the latest build,
then click on "krita-packages" under "Artifacts"; you need to be logged in.) If
you manage to trigger the crash in it, there will be detailed log output in
DebugView (krita.exe) or the console (krita.com). This can help pinpoint the
actual error.
(If you want to try this, let's talk on IRC.)
^ ASan = address sanitizer, which is a tool to help catch memory errors such as
use-after-free.
--
You are receiving this mail because:
You are watching all bug changes.
