3 ms·
eh, I daily-drive a -fsanitize=address -fsanitize=undefined build of Qt and actual memory bugs are almost never a thing - I think the only time I had some were
by jcelerier 9mo ago
eh, I daily-drive a -fsanitize=address -fsanitize=undefined build of Qt and actual memory bugs are almost never a thing - I think the only time I had some were in tooling executables such as qmllint, but not in the framework itself. Most of the bugs by large are more "behaviour" bugs.
- adrianN 9mo agoI’m impressed that QT runs clean enough under ubsan for daily use.
- jcelerier 9mo agoubsan definitely has some warnings due to a few "technically UB" patterns used as optimizations in Qt as they are known-working on every target platform under the sun, but yeah, no crashes :) I'm only using this configuration for the software I develop though (+ libc++ debug mode) as it's painfully slow, but it exercises the Qt codebase in depth.
- fransje26 9mo agoGood to know! Which version of Qt are you using?
- jcelerier 9mo agoI regularly update, right now 6.10.1 + a few patches
- rubymamis 9mo agoHere is another bug that led to crush thatt I reported while developing my block editor: https://qt-project.atlassian.net/browse/QTBUG-124572 https://qt-project.atlassian.net/browse/QTBUG-124572