tst_QMessageLogger: disable Android once and for all

The messages said "This test crashes on Android" bu tit appears the
problem is not a crash, but that the executable can't be executed. The
file appears to be present and yet execve() is producing ENOENT (No such
file or directory). That probably means it's the interpreter stored in
the ELF header's dynamic section that is not found.

Fixing that is SEP[1].

[1] https://en.wikipedia.org/wiki/Somebody_else%27s_problem

Pick-to: 6.9
Change-Id: I3025825c5e00f47a5a40fffd53c47131db3676dc
Reviewed-by: Assam Boudjelthia <assam.boudjelthia@qt.io>
This commit is contained in:
Thiago Macieira 2025-01-18 08:49:28 -08:00
parent baddc0a195
commit 40ad963e1a

View File

@ -846,7 +846,7 @@ void tst_qmessagehandler::qMessagePattern()
QSKIP("This test requires QProcess support");
#else
#ifdef Q_OS_ANDROID
QSKIP("This test crashes on Android");
QSKIP("This test is disabled on Android");
#endif
QFETCH(QString, pattern);
QFETCH(bool, valid);
@ -892,7 +892,7 @@ void tst_qmessagehandler::setMessagePattern()
QSKIP("This test requires QProcess support");
#else
#ifdef Q_OS_ANDROID
QSKIP("This test crashes on Android");
QSKIP("This test is disabled on Android");
#endif
//
@ -1060,8 +1060,8 @@ void tst_qmessagehandler::formatLogMessage()
QString tst_qmessagehandler::backtraceHelperPath()
{
#ifdef Q_OS_ANDROID
QString appExe(QCoreApplication::applicationDirPath()
+ QLatin1String("/lib" BACKTRACE_HELPER_NAME ".so"));
qFatal("Launching the helper (which does exist) produces 'No such file or directory'.");
QString appExe;
#else
QString appExe(QCoreApplication::applicationDirPath()
+ QLatin1String("/" BACKTRACE_HELPER_NAME));