Hi, everyone!

I've just started using Krita a few weeks ago on OSX and it crashes from time to time. The thing is: I don't always know how to reproduce the steps that lead to the crash...

What would be the best things to do to track the source of the problem? I guess there is a log file somewhere that helps, but should I use other tools too? I'm quite familiar with C++, but not with Qt development. I've also used tools such as gdb and valgrind, but I'm not an expert. Should I use one of these two tools? Or another one? Thanks for any pointer!

Note that I have built Krita from source and I can toy with the code if necessary.

And Happy New Year!

Well, on Linux you canuse gdb, or if you have the right libraries, DrKonqi will come with a backtrace. For windows we have drmingw: https://docs.krita.org/Dr._Mingw_debugger

But I don't know what would be used on OSX...

For those crashes it would probably best to make it a habit to run Krita in lldb. Just start lldb like this:

lldb krita.app/Contents/MacOS/krita,

type run, do whatever happens and then when you get a crash, you get a backtrace in lldb. (lldb, not gdb, because Krita is built with clang on OSX). Make sure that you build with RelWithDebInfo or FullDebug as cmake build type.

I'm not exactly a guru when it comes to OSX, so there might be a better way to get backtraces, but this is the method I'm familiar with