From 708527342c6697ef47021607a1986d7a2f5ca566 Mon Sep 17 00:00:00 2001 From: Pino Toscano Date: Sat, 13 May 2023 12:12:14 +0100 Subject: [PATCH] Avoid unconditional PATH_MAX usage Forwarded: no Last-Update: 2020-04-19 Use a "safe" size in case PATH_MAX is not defined; in the end, this should not be used, as a allocating realpath() will be used instead. Gbp-Pq: Name path_max.diff --- src/corelib/io/qfilesystemengine_unix.cpp | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/corelib/io/qfilesystemengine_unix.cpp b/src/corelib/io/qfilesystemengine_unix.cpp index 58e06ee1c..b0e123a04 100644 --- a/src/corelib/io/qfilesystemengine_unix.cpp +++ b/src/corelib/io/qfilesystemengine_unix.cpp @@ -689,7 +689,11 @@ QFileSystemEntry QFileSystemEngine::canonicalName(const QFileSystemEntry &entry, Q_UNUSED(data); return QFileSystemEntry(slowCanonicalized(absoluteName(entry).filePath())); #else +#ifdef PATH_MAX char stack_result[PATH_MAX+1]; +#else + char stack_result[4096+1]; +#endif char *resolved_name = nullptr; # if defined(Q_OS_DARWIN) || defined(Q_OS_ANDROID) // On some Android and macOS versions, realpath() will return a path even if -- 2.30.2