tst_qlogging: Skip backtrace tests under ASan
ASan inserts a lot of function calls in between our calls, so they end up in the backtrace and cause unexpected results. Similar to c672f148dbf179f2e0ac94dfac7d329d50a3e4a3. Fixes: QTBUG-109559 Change-Id: I69ecc04064514f939896fffd1732dd2bc0317ae4 Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io> (cherry picked from commit 6e68b4d838f35b75cbf1a79863b52f43d08defe9)
This commit is contained in:
parent
8680d45bac
commit
5036562bd2
@ -725,6 +725,8 @@ void tst_qmessagehandler::qMessagePattern_data()
|
|||||||
#ifdef __GLIBC__
|
#ifdef __GLIBC__
|
||||||
# if QT_CONFIG(static)
|
# if QT_CONFIG(static)
|
||||||
// These test cases don't work with static Qt builds
|
// These test cases don't work with static Qt builds
|
||||||
|
# elif defined(QT_ASAN_ENABLED)
|
||||||
|
// These tests produce far more call frames under ASan
|
||||||
# else
|
# else
|
||||||
# ifndef QT_NO_DEBUG
|
# ifndef QT_NO_DEBUG
|
||||||
QList<QByteArray> expectedBacktrace = {
|
QList<QByteArray> expectedBacktrace = {
|
||||||
|
Loading…
x
Reference in New Issue
Block a user