clang analyzer: Don't warn about Xmalloc(0)

This will prevent a number of false positives in where clang's static analysis reports about calls to malloc(0). Signed-off-by: Jeremy Huddleston <jeremyhu@apple.com> Backported-to-NX-by: Ulrich Sibiller <uli42@gmx.de>

clang analyzer: Don't warn about Xmalloc(0)
5062342d · Jeremy Huddleston · Ulrich Sibiller · c19cda6d · 5062342d
Commit 5062342d authored May 03, 2011 by Jeremy Huddleston Committed by Ulrich Sibiller Oct 19, 2016
Hide whitespace changes
Inline Side-by-side

Showing with 1 addition and 1 deletion

Xlibint.h nx-X11/lib/X11/Xlibint.h +1 -1

No files found.
--- a/nx-X11/lib/X11/Xlibint.h
+++ b/nx-X11/lib/X11/Xlibint.h
@@ -367,7 +367,7 @@ extern LockInfoPtr _Xglobal_lock;
 * define MALLOC_0_RETURNS_NULL.  This is necessary because some
 * Xlib code expects malloc(0) to return a valid pointer to storage.
 */
-#ifdef MALLOC_0_RETURNS_NULL
+#if defined(MALLOC_0_RETURNS_NULL) || defined(__clang_analyzer__)

 # define Xmalloc(size) malloc(((size) == 0 ? 1 : (size)))
 # define Xrealloc(ptr, size) realloc((ptr), ((size) == 0 ? 1 : (size)))