summaryrefslogtreecommitdiff
path: root/ipc
diff options
context:
space:
mode:
authorathenian200 <athenian200@outlook.com>2019-10-01 19:15:26 -0500
committerathenian200 <athenian200@outlook.com>2019-10-21 04:53:40 -0500
commitf105b741e549e2c2b985e1458ff6153c3d13929a (patch)
tree54c87bc6b892e81ff741c2b5c81bf6c38b74e1de /ipc
parent4105ebb6ed85aaffec5e4469a939945fb9eea066 (diff)
downloaduxp-f105b741e549e2c2b985e1458ff6153c3d13929a.tar.gz
MoonchildProductions#1251 - Part 5: Fix POSIX compliance issue in process_util.h.
https://bugzilla.mozilla.org/show_bug.cgi?id=1364865 Solaris doesn't define NAME_MAX because if you read the current POSIX standard literally, no system that supports multiple file systems or networking should be defining it. It's a pedantic choice given that they USED to define NAME_MAX, but Solaris always did take POSIX compliance seriously, for better or worse.
Diffstat (limited to 'ipc')
-rw-r--r--ipc/chromium/src/base/process_util.h4
1 files changed, 3 insertions, 1 deletions
diff --git a/ipc/chromium/src/base/process_util.h b/ipc/chromium/src/base/process_util.h
index 2b257b587c..9b1e4fed5f 100644
--- a/ipc/chromium/src/base/process_util.h
+++ b/ipc/chromium/src/base/process_util.h
@@ -44,10 +44,12 @@ typedef PROCESSENTRY32 ProcessEntry;
typedef IO_COUNTERS IoCounters;
#elif defined(OS_POSIX)
// TODO(port): we should not rely on a Win32 structure.
+// Using NAME_MAX here would raise POSIX compliance issues
+// (see Mozilla bug 1364865).
struct ProcessEntry {
int pid;
int ppid;
- char szExeFile[NAME_MAX + 1];
+ char szExeFile[_POSIX_PATH_MAX + 1];
};
struct IoCounters {