https://bugs.kde.org/show_bug.cgi?id=385640
--- Comment #9 from RJVB <rjvber...@gmail.com> --- > > https://woboq.com/blog/nice-debug-output-with-qt.html -- grep for > "backtrace" -- you can enable them for e.g. warnings exclusively. It turns out that seting QT_MESSAGE_PATTERN from the code has the intended effect, but the %{backtrace} feature is only available on glib-based platforms. It also doesn't provide very useful backtraces; no demangling, no filenames let alone line numbers. A very simple test (qInfo() called from a function loggertest() called from main() in an application called qlogging prints this: ?qlogging?|?qlogging?|__libc_start_main|?qlogging? (even when built with -O0 -g) -- You are receiving this mail because: You are watching all bug changes.
